Devices, methods, and graphical user interfaces for accessing notifications

ABSTRACT

An electronic device with a display and a touch-sensitive surface receives notification(s) while the device is in a screen-off state. After receiving the notification(s), the device detects an input for waking the device to a screen-on state. In response, the device transitions to the screen-on state and displays the notification(s) on a wake screen user interface. The device further detects another input for dismissing the wake screen user interface and ceases to display the wake screen user interface. Afterwards, the device detects a third input for redisplaying the wake screen user interface. In response, upon determining that the third input meets notification-clearance criteria, the device redisplays the wake screen user interface without displaying at least one of the notification(s); and upon determining that the third input does not meet the notification-clearance criteria: the device redisplays the wake screen user interface and redisplays at least one of notification(s).

RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application No.62/507,181, filed May 16, 2017, titled, “Devices, Methods, and GraphicalUser Interfaces for Accessing Notifications,” which is herebyincorporated by reference in its entirety.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices withtouch-sensitive surfaces that include user interfaces for displayingnotifications.

BACKGROUND

The use of portable electronic devices has increased significantly inrecent years, with many applications typically residing in the memory ofsuch devices. Exemplary applications include messaging applications,calendar applications and social media applications. Electronic devicesoften receive communications for these applications, which containinformation of importance to users. These electronic devices then oftenprovide notifications that correspond to the received communications.

Exemplary communications include instant messages, calendar invitations,social media updates, microblog posts and news stories. Exemplarynotifications associated with these communications may include digitalimages, video, text, icons, control elements (such as buttons) and/orother graphics to notify users of the receipt of these communications.Exemplary applications receiving communications and generatingnotifications include instant messaging applications (e.g., iMessagefrom Apple Inc. of Cupertino, Calif.), calendar applications (e.g., iCalor Calendar from Apple Inc. of Cupertino, Calif.), social networkingapplications, microblogging applications, and news applications.

But user interfaces for accessing notifications, and methods ofnavigating to and from such interfaces, are cumbersome and inefficient.For example, the notifications may be displayed in a confusing manner,and navigation to and from interfaces that contain notifications mayalso be confusing. These methods take longer than necessary, therebywasting energy. This latter consideration is particularly important inbattery-operated devices.

SUMMARY

Accordingly, there is a need for electronic devices with faster, moreefficient methods and interfaces for accessing notifications. Suchmethods and interfaces optionally complement or replace conventionalmethods for accessing notifications. Such methods and interfaces reducethe number, extent, and/or nature of the inputs from a user and producea more efficient human-machine interface. For battery-operated devices,such methods and interfaces conserve power and increase the time betweenbattery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device is a personal electronic device(e.g., a wearable electronic device, such as a watch). In someembodiments, the device has a touchpad. In some embodiments, the devicehas a touch-sensitive display (also known as a “touch screen” or“touch-screen display”). In some embodiments, the device has a graphicaluser interface (GUI), one or more processors, memory and one or moremodules, programs or sets of instructions stored in the memory forperforming multiple functions. In some embodiments, the user interactswith the GUI primarily through stylus and/or finger contacts andgestures on the touch-sensitive surface. In some embodiments, thefunctions optionally include image editing, drawing, presenting, wordprocessing, spreadsheet making, game playing, telephoning, videoconferencing, e-mailing, instant messaging, workout support, digitalphotographing, digital videoing, web browsing, digital music playing,note taking, and/or digital video playing. Executable instructions forperforming these functions are, optionally, included in a non-transitorycomputer readable storage medium or other computer program productconfigured for execution by one or more processors.

In accordance with some embodiments, a method is performed at a devicehaving a display and a touch-sensitive surface. The method includes:while the device is in a screen-off state, receiving one or morenotifications; after receiving the one or more notifications, detectinga first input from a user for waking the device from the screen-offstate to a screen-on state; in response to detecting the first input forwaking the device from the screen-off state to the screen-on state:transitioning the device from the screen-off state to the screen-onstate; displaying a wake screen user interface on the display; anddisplaying the one or more notifications on the wake screen userinterface; while displaying the wake screen user interface and while atleast one of the one or more notifications remains displayed on the wakescreen user interface, detecting a second input for dismissing the wakescreen user interface; in response to detecting the second input fordismissing the wake screen user interface, ceasing to display the wakescreen user interface and the at least one of the one or morenotifications; after ceasing to display the wake screen user interfaceand the at least one of the one or more notifications in response to thesecond input, detecting a third input for redisplaying the wake screenuser interface; in response to detecting the third input forredisplaying the wake screen user interface: in accordance with adetermination that the third input meets notification-clearancecriteria, wherein the notification-clearance criteria require that thethird input is detected at a time that is (1) after a respectivenotification of the one or more notifications has been cleared throughdirect user interaction with the respective notification or anapplication that corresponds to the respective notification and (2)after the device has transitioned from the screen-on state to thescreen-off state at least once since the detection of the second input,redisplaying the wake screen user interface without displaying the atleast one of the one or more notifications on the redisplayed wakescreen user interface; and in accordance with a determination that thethird input does not meet the notification-clearance criteria:redisplaying the wake screen user interface, and redisplaying the atleast one of the one or more notifications on the redisplayed wakescreen user interface.

In accordance with some embodiments, a method is performed at a devicehaving a display and a touch-sensitive surface. The method includes:displaying a first user interface, including displaying one or moremissed notifications in a first scrollable arrangement on the first userinterface; while displaying the first user interface with the one ormore missed notifications, detecting a first swipe gesture, includingdetecting a first contact at a location on the touch-sensitive surfacethat corresponds to the first scrollable arrangement, and detectingfirst movement of the first contact across the touch-sensitive surfacein a first direction; in response to detecting the first swipe gesture,scrolling the first scrollable arrangement in accordance with the firstmovement of the first contact; after scrolling the first scrollablearrangement in accordance with the first movement of the first contact,detecting a second swipe gesture, including detecting a second contactat a location on the touch-sensitive surface that corresponds to thefirst scrollable arrangement, and detecting second movement of thesecond contact across the touch-sensitive surface in the firstdirection; in response to detecting the second swipe gesture: inaccordance with a determination that the second movement of the secondcontact meets notification-history- display criteria, wherein thenotification-history-display criteria require (1) that the secondmovement of the second contact is detected after an end of the firstscrollable arrangement has been reached in accordance with the firstmovement of the first contact and (2) that the second movement exceeds afirst threshold amount of movement in the first direction, displaying aplurality of previously received notifications that are distinct fromthe one or more missed notifications in a second scrollable arrangementon the first user interface; and, in accordance with the determinationthat the second movement of the first contact does not meet thenotification-history-display criteria, forgoing displaying the pluralityof previously received notifications.

In accordance with some embodiments, a method is performed at a devicehaving a display and a touch-sensitive surface. The method includes:displaying a first user interface on the display; displaying a firstuser interface object overlaid on a first portion of the first userinterface; while displaying the first user interface object overlaid onthe first portion of the first user interface, detecting a first inputfor displaying a cover sheet user interface, where the cover sheet userinterface includes a first content object and a second content objectdisplayed on a background object; in response to detecting the firstinput for displaying the cover sheet user interface, moving the coversheet user interface across the display in a first direction, including:moving the background object of the cover sheet user interface acrossthe display; in accordance with a determination that the first userinterface object has not reached a predefined threshold positionrelative to the cover sheet user interface, moving the first contentobject and the second content object with the background object whilemaintaining a current position of the first user interface object on thedisplay; and, in accordance with a determination that the first userinterface object has reached the predefined threshold position relativeto the cover sheet user interface, moving the first user interfaceobject with the background object.

In accordance with some embodiments, a method is performed at a devicehaving a display and a touch-sensitive surface. The method includes:while the device is in a screen-off state, detecting a first input forwaking the device from the screen-off state to a screen-on state; and inresponse to detecting the first input for waking the device from thescreen-off state to the screen-on state: transitioning the device fromthe screen-off state to the screen-on state, and displaying a wakescreen user interface on the display; while displaying the wake screenuser interface, detecting a first swipe gesture on the touch-sensitivesurface, including detecting a first contact on the touch-sensitivesurface and detecting movement of the first contact across thetouch-sensitive surface; in response to detecting the first swipegesture: ceasing to display the wake screen user interface; anddisplaying a first user interface, wherein: in accordance with adetermination that the first swipe gesture is in a first direction, thedisplayed first user interface is a mini-application-object userinterface, wherein the mini-application-object user interface includesone or more mini-application objects that each provide a subset offunctions of a corresponding application without launching thecorresponding application; and, in accordance with a determination thatthe first swipe gesture is in a second direction that is opposite thefirst direction, the displayed first user interface is a control paneluser interface, wherein the control panel user interface includes one ormore device controls for controlling one or more device functions of thedevice.

In accordance with some embodiments, an electronic device includes adisplay, a touch-sensitive surface, optionally one or more sensors todetect intensities of contacts with the touch-sensitive surface,optionally one or more tactile output generators, one or moreprocessors, and memory storing one or more programs; the one or moreprograms are configured to be executed by the one or more processors andthe one or more programs include instructions for performing or causingperformance of the operations of any of the methods described herein. Inaccordance with some embodiments, a computer readable storage medium hasstored therein instructions, which, when executed by an electronicdevice with a display, a touch-sensitive surface, optionally one or moresensors to detect intensities of contacts with the touch-sensitivesurface, and optionally one or more tactile output generators, cause thedevice to perform or cause performance of the operations of any of themethods described herein. In accordance with some embodiments, agraphical user interface on an electronic device with a display, atouch-sensitive surface, optionally one or more sensors to detectintensities of contacts with the touch-sensitive surface, optionally oneor more tactile output generators, a memory, and one or more processorsto execute one or more programs stored in the memory includes one ormore of the elements displayed in any of the methods described herein,which are updated in response to inputs, as described in any of themethods described herein. In accordance with some embodiments, anelectronic device includes: a display, a touch-sensitive surface,optionally one or more sensors to detect intensities of contacts withthe touch-sensitive surface, and optionally one or more tactile outputgenerators; and means for performing or causing performance of theoperations of any of the methods described herein. In accordance withsome embodiments, an information processing apparatus, for use in anelectronic device with a display, a touch-sensitive surface, optionallyone or more sensors to detect intensities of contacts with thetouch-sensitive surface, and optionally one or more tactile outputgenerators, includes means for performing or causing performance of theoperations of any of the methods described herein.

Thus, electronic devices with displays, touch-sensitive surfaces,optionally one or more sensors to detect intensities of contacts withthe touch-sensitive surface, optionally one or more tactile outputgenerators, optionally one or more device orientation sensors, areprovided with improved interfaces for accessing notifications andimproved navigation to and from such interfaces, thereby increasing theeffectiveness, efficiency, and user satisfaction with such devices. Suchmethods and interfaces may complement or replace conventional methodsfor providing accessing notifications.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display, in accordance with some embodiments.

FIG. 1B is a block diagram illustrating example components for eventhandling, in accordance with some embodiments.

FIG. 1C is a block diagram illustrating a tactile output module, inaccordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touchscreen, in accordance with some embodiments.

FIG. 3 is a block diagram of an example multifunction device with adisplay and a touch-sensitive surface, in accordance with someembodiments.

FIG. 4A illustrates an example user interface for a menu of applicationson a portable multifunction device, in accordance with some embodiments.

FIG. 4B illustrates an example user interface for a multifunction devicewith a touch-sensitive surface that is separate from the display, inaccordance with some embodiments.

FIGS. 4C-4E illustrate examples of dynamic intensity thresholds, inaccordance with some embodiments.

FIGS. 5A1-5A4, 5B-5EB, 5EC1-5EC4, 5ED-5HR illustrate example userinterfaces for providing access to notifications on a cover sheet userinterface in accordance with some embodiments.

FIGS. 6A-6G are flow diagrams of a process for clearing sets ofnotifications, in accordance with some embodiments.

FIGS. 7A-7E are flow diagrams of a process for displaying notificationhistory, in accordance with some embodiments.

FIGS. 8A-8C are flow diagrams of a process for displaying updatinginformation from an application in a floating banner, in accordance withsome embodiments.

FIGS. 9A-9C are flow diagrams of a process for navigation using a coversheet, in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

A number of different approaches for navigating to, displaying, and/orinteracting with notification content and user interfaces that displaynotifications are described herein. Using one or more of theseapproaches (optionally in conjunction with each other) reduces thenumber, extent, and/or nature of the inputs from a user and provides amore efficient human-machine interface. For battery-operated devices,these improvements conserve power and increase the time between batterycharges. These approaches describe improved methods for:

-   -   clearing individual notifications and clearing sets of        notifications;    -   displaying notification history;    -   displaying updating information from an application in a        floating banner; and    -   navigating from a user interface that displays notifications to        adjacent user interfaces that display device controls and/or        application controls.

The methods, devices, and GUIs described herein display notifications ona cover sheet to present recent information received and/or generated byapplications installed on a device, which makes the user-deviceinterface more efficient in multiple ways. For example, they providemore efficient ways to retain sets of notifications, clear sets ofnotifications, display missed notifications, display previously clearednotifications in a notification history, access information from anactive mode of an application using a banner that is displayed in userinterfaces other than the application user interface, and accessadditional user interfaces from a cover sheet user interface.

Below, FIGS. 1A-1B, 2, and 3 provide a description of example devices.FIGS. 4A-4B and 5A-5HR illustrate example user interfaces for providingaccess to notifications on a cover sheet user interface. FIGS. 6A-6Gillustrate a flow diagram of a method of clearing notifications inaccordance with some embodiments. FIGS. 7A-7E illustrate a flow diagramof a method of displaying notification history in accordance with someembodiments. FIGS. 8A-8C illustrate a flow diagram of a method ofdisplaying updating information from an application in a floating bannerin accordance with some embodiments. FIGS. 9A-9C illustrate a flowdiagram of a method of navigation using a cover sheet in accordance withsome embodiments. The user interfaces in FIGS. 5A-5HR are used toillustrate the processes in FIGS. 6A-6G, 7A-7E, 8A-8C, and 9A-9C.

Example Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact, unless the contextclearly indicates otherwise.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Example embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch-screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch-screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a note taking application, a drawing application,a presentation application, a word processing application, a websitecreation application, a disk authoring application, a spreadsheetapplication, a gaming application, a telephone application, a videoconferencing application, an e-mail application, an instant messagingapplication, a workout support application, a photo managementapplication, a digital camera application, a digital video cameraapplication, a web browsing application, a digital music playerapplication, and/or a digital video player application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display system112 is sometimes called a “touch screen” for convenience, and issometimes simply called a touch-sensitive display. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input or control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more intensity sensors 165 for detectingintensities of contacts on device 100 (e.g., a touch-sensitive surfacesuch as touch-sensitive display system 112 of device 100). Device 100optionally includes one or more tactile output generators 167 forgenerating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user. Using tactile outputs toprovide haptic feedback to a user enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, a tactile output pattern specifies characteristicsof a tactile output, such as the amplitude of the tactile output, theshape of a movement waveform of the tactile output, the frequency of thetactile output, and/or the duration of the tactile output.

When tactile outputs with different tactile output patterns aregenerated by a device (e.g., via one or more tactile output generatorsthat move a moveable mass to generate tactile outputs), the tactileoutputs may invoke different haptic sensations in a user holding ortouching the device. While the sensation of the user is based on theuser's perception of the tactile output, most users will be able toidentify changes in waveform, frequency, and amplitude of tactileoutputs generated by the device. Thus, the waveform, frequency andamplitude can be adjusted to indicate to the user that differentoperations have been performed. As such, tactile outputs with tactileoutput patterns that are designed, selected, and/or engineered tosimulate characteristics (e.g., size, material, weight, stiffness,smoothness, etc.); behaviors (e.g., oscillation, displacement,acceleration, rotation, expansion, etc.); and/or interactions (e.g.,collision, adhesion, repulsion, attraction, friction, etc.) of objectsin a given environment (e.g., a user interface that includes graphicalfeatures and objects, a simulated physical environment with virtualboundaries and virtual objects, a real physical environment withphysical boundaries and physical objects, and/or a combination of any ofthe above) will, in some circumstances, provide helpful feedback tousers that reduces input errors and increases the efficiency of theuser's operation of the device. Additionally, tactile outputs are,optionally, generated to correspond to feedback that is unrelated to asimulated physical characteristic, such as an input threshold or aselection of an object. Such tactile outputs will, in somecircumstances, provide helpful feedback to users that reduces inputerrors and increases the efficiency of the user's operation of thedevice.

In some embodiments, a tactile output with a suitable tactile outputpattern serves as a cue for the occurrence of an event of interest in auser interface or behind the scenes in a device. Examples of the eventsof interest include activation of an affordance (e.g., a real or virtualbutton, or toggle switch) provided on the device or in a user interface,success or failure of a requested operation, reaching or crossing aboundary in a user interface, entry into a new state, switching of inputfocus between objects, activation of a new mode, reaching or crossing aninput threshold, detection or recognition of a type of input or gesture,etc. In some embodiments, tactile outputs are provided to serve as awarning or an alert for an impending event or outcome that would occurunless a redirection or interruption input is timely detected. Tactileoutputs are also used in other contexts to enrich the user experience,improve the accessibility of the device to users with visual or motordifficulties or other accessibility needs, and/or improve efficiency andfunctionality of the user interface and/or the device. Tactile outputsare optionally accompanied with audio outputs and/or visible userinterface changes, which further enhance a user's experience when theuser interacts with a user interface and/or the device, and facilitatebetter conveyance of information regarding the state of the userinterface and/or the device, and which reduce input errors and increasethe efficiency of the user's operation of the device.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, firmware, or a combination thereof,including one or more signal processing and/or application specificintegrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 102 by othercomponents of device 100, such as CPU(s) 120 and the peripheralsinterface 118, is, optionally, controlled by memory controller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU(s) 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU(s) 120, and memorycontroller 122 are, optionally, implemented on a single chip, such aschip 104. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch-sensitive display system 112 and other input or control devices116, with peripherals interface 118. I/O subsystem 106 optionallyincludes display controller 156, optical sensor controller 158,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input or controldevices 116 optionally include physical buttons (e.g., push buttons,rocker buttons, etc.), dials, slider switches, joysticks, click wheels,and so forth. In some alternate embodiments, input controller(s) 160are, optionally, coupled with any (or none) of the following: akeyboard, infrared port, USB port, stylus, and/or a pointer device suchas a mouse. The one or more buttons (e.g., 208, FIG. 2) optionallyinclude an up/down button for volume control of speaker 111 and/ormicrophone 113. The one or more buttons optionally include a push button(e.g., 206, FIG. 2).

Touch-sensitive display system 112 provides an input interface and anoutput interface between the device and a user. Display controller 156receives and/or sends electrical signals from/to touch-sensitive displaysystem 112. Touch-sensitive display system 112 displays visual output tothe user. The visual output optionally includes graphics, text, icons,video, and any combination thereof (collectively termed “graphics”). Insome embodiments, some or all of the visual output corresponds to userinterface objects. As used herein, the term “affordance” refers to auser-interactive graphical user interface object (e.g., a graphical userinterface object that is configured to respond to inputs directed towardthe graphical user interface object). Examples of user-interactivegraphical user interface objects include, without limitation, a button,slider, icon, selectable menu item, switch, hyperlink, or other userinterface control.

Touch-sensitive display system 112 has a touch-sensitive surface, sensoror set of sensors that accepts input from the user based on hapticand/or tactile contact. Touch-sensitive display system 112 and displaycontroller 156 (along with any associated modules and/or sets ofinstructions in memory 102) detect contact (and any movement or breakingof the contact) on touch-sensitive display system 112 and converts thedetected contact into interaction with user-interface objects (e.g., oneor more soft keys, icons, web pages or images) that are displayed ontouch-sensitive display system 112. In some embodiments, a point ofcontact between touch-sensitive display system 112 and the usercorresponds to a finger of the user or a stylus.

Touch-sensitive display system 112 optionally uses LCD (liquid crystaldisplay) technology, LPD (light emitting polymer display) technology, orLED (light emitting diode) technology, although other displaytechnologies are used in other embodiments. Touch-sensitive displaysystem 112 and display controller 156 optionally detect contact and anymovement or breaking thereof using any of a plurality of touch sensingtechnologies now known or later developed, including but not limited tocapacitive, resistive, infrared, and surface acoustic wave technologies,as well as other proximity sensor arrays or other elements fordetermining one or more points of contact with touch-sensitive displaysystem 112. In some embodiments, projected mutual capacitance sensingtechnology is used, such as that found in the iPhone®, iPod Touch®, andiPad® from Apple Inc. of Cupertino, Calif.

Touch-sensitive display system 112 optionally has a video resolution inexcess of 100 dpi. In some embodiments, the touch screen videoresolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater).The user optionally makes contact with touch-sensitive display system112 using any suitable object or appendage, such as a stylus, a finger,and so forth. In some embodiments, the user interface is designed towork with finger-based contacts and gestures, which can be less precisethan stylus-based input due to the larger area of contact of a finger onthe touch screen. In some embodiments, the device translates the roughfinger-based input into a precise pointer/cursor position or command forperforming the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch-sensitive displaysystem 112 or an extension of the touch-sensitive surface formed by thetouch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled with optical sensor controller158 in I/O subsystem 106. Optical sensor(s) 164 optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor(s) 164 receive light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor(s) 164 optionally capturestill images and/or video. In some embodiments, an optical sensor islocated on the back of device 100, opposite touch-sensitive displaysystem 112 on the front of the device, so that the touch screen isenabled for use as a viewfinder for still and/or video imageacquisition. In some embodiments, another optical sensor is located onthe front of the device so that the user's image is obtained (e.g., forselfies, for videoconferencing while the user views the other videoconference participants on the touch screen, etc.).

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled withintensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor(s) 165 optionally include one or more piezoresistive straingauges, capacitive force sensors, electric force sensors, piezoelectricforce sensors, optical force sensors, capacitive touch-sensitivesurfaces, or other intensity sensors (e.g., sensors used to measure theforce (or pressure) of a contact on a touch-sensitive surface). Contactintensity sensor(s) 165 receive contact intensity information (e.g.,pressure information or a proxy for pressure information) from theenvironment. In some embodiments, at least one contact intensity sensoris collocated with, or proximate to, a touch-sensitive surface (e.g.,touch-sensitive display system 112). In some embodiments, at least onecontact intensity sensor is located on the back of device 100, oppositetouch-screen display system 112 which is located on the front of device100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled with peripherals interface118. Alternately, proximity sensor 166 is coupled with input controller160 in I/O subsystem 106. In some embodiments, the proximity sensorturns off and disables touch-sensitive display system 112 when themultifunction device is placed near the user's ear (e.g., when the useris making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled withhaptic feedback controller 161 in I/O subsystem 106. In someembodiments, tactile output generator(s) 167 include one or moreelectroacoustic devices such as speakers or other audio componentsand/or electromechanical devices that convert energy into linear motionsuch as a motor, solenoid, electroactive polymer, piezoelectricactuator, electrostatic actuator, or other tactile output generatingcomponent (e.g., a component that converts electrical signals intotactile outputs on the device). Tactile output generator(s) 167 receivetactile feedback generation instructions from haptic feedback module 133and generates tactile outputs on device 100 that are capable of beingsensed by a user of device 100. In some embodiments, at least onetactile output generator is collocated with, or proximate to, atouch-sensitive surface (e.g., touch-sensitive display system 112) and,optionally, generates a tactile output by moving the touch-sensitivesurface vertically (e.g., in/out of a surface of device 100) orlaterally (e.g., back and forth in the same plane as a surface of device100). In some embodiments, at least one tactile output generator sensoris located on the back of device 100, opposite touch-sensitive displaysystem 112, which is located on the front of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled with peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled with an inputcontroller 160 in I/O subsystem 106. In some embodiments, information isdisplayed on the touch-screen display in a portrait view or a landscapeview based on an analysis of data received from the one or moreaccelerometers. Device 100 optionally includes, in addition toaccelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASSor other global navigation system) receiver (not shown) for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, haptic feedback module (orset of instructions) 133, text input module (or set of instructions)134, Global Positioning System (GPS) module (or set of instructions)135, and applications (or sets of instructions) 136. Furthermore, insome embodiments, memory 102 stores device/global internal state 157, asshown in FIGS. 1A and 3. Device/global internal state 157 includes oneor more of: active application state, indicating which applications, ifany, are currently active; display state, indicating what applications,views or other information occupy various regions of touch-sensitivedisplay system 112; sensor state, including information obtained fromthe device's various sensors and other input or control devices 116; andlocation and/or positional information concerning the device's locationand/or attitude.

Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used in some iPhone®, iPod Touch®, and iPad® devicesfrom Apple Inc. of Cupertino, Calif. In some embodiments, the externalport is a Lightning connector that is the same as, or similar to and/orcompatible with the Lightning connector used in some iPhone®, iPodTouch®, and iPad® devices from Apple Inc. of Cupertino, Calif.

Contact/motion module 130 optionally detects contact withtouch-sensitive display system 112 (in conjunction with displaycontroller 156) and other touch-sensitive devices (e.g., a touchpad orphysical click wheel). Contact/motion module 130 includes varioussoftware components for performing various operations related todetection of contact (e.g., by a finger or by a stylus), such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts or stylus contacts) or to multiplesimultaneous contacts (e.g., “multitouch”/multiple finger contacts). Insome embodiments, contact/motion module 130 and display controller 156detect contact on a touchpad.

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event. Similarly, tap,swipe, drag, and other gestures are optionally detected for a stylus bydetecting a particular contact pattern for the stylus.

In some embodiments, detecting a finger tap gesture depends on thelength of time between detecting the finger-down event and the finger-upevent, but is independent of the intensity of the finger contact betweendetecting the finger-down event and the finger-up event. In someembodiments, a tap gesture is detected in accordance with adetermination that the length of time between the finger-down event andthe finger-up event is less than a predetermined value (e.g., less than0.1, 0.2, 0.3, 0.4 or 0.5 seconds), independent of whether the intensityof the finger contact during the tap meets a given intensity threshold(greater than a nominal contact-detection intensity threshold), such asa light press or deep press intensity threshold. Thus, a finger tapgesture can satisfy particular input criteria that do not require thatthe characteristic intensity of a contact satisfy a given intensitythreshold in order for the particular input criteria to be met. Forclarity, the finger contact in a tap gesture typically needs to satisfya nominal contact-detection intensity threshold, below which the contactis not detected, in order for the finger-down event to be detected. Asimilar analysis applies to detecting a tap gesture by a stylus or othercontact. In cases where the device is capable of detecting a finger orstylus contact hovering over a touch sensitive surface, the nominalcontact-detection intensity threshold optionally does not correspond tophysical contact between the finger or stylus and the touch sensitivesurface.

The same concepts apply in an analogous manner to other types ofgestures. For example, a swipe gesture, a pinch gesture, a depinchgesture, and/or a long press gesture are optionally detected based onthe satisfaction of criteria that are either independent of intensitiesof contacts included in the gesture, or do not require that contact(s)that perform the gesture reach intensity thresholds in order to berecognized. For example, a swipe gesture is detected based on an amountof movement of one or more contacts; a pinch gesture is detected basedon movement of two or more contacts towards each other; a depinchgesture is detected based on movement of two or more contacts away fromeach other; and a long press gesture is detected based on a duration ofthe contact on the touch-sensitive surface with less than a thresholdamount of movement. As such, the statement that particular gesturerecognition criteria do not require that the intensity of the contact(s)meet a respective intensity threshold in order for the particulargesture recognition criteria to be met means that the particular gesturerecognition criteria are capable of being satisfied if the contact(s) inthe gesture do not reach the respective intensity threshold, and arealso capable of being satisfied in circumstances where one or more ofthe contacts in the gesture do reach or exceed the respective intensitythreshold. In some embodiments, a tap gesture is detected based on adetermination that the finger-down and finger-up event are detectedwithin a predefined time period, without regard to whether the contactis above or below the respective intensity threshold during thepredefined time period, and a swipe gesture is detected based on adetermination that the contact movement is greater than a predefinedmagnitude, even if the contact is above the respective intensitythreshold at the end of the contact movement. Even in implementationswhere detection of a gesture is influenced by the intensity of contactsperforming the gesture (e.g., the device detects a long press morequickly when the intensity of the contact is above an intensitythreshold or delays detection of a tap input when the intensity of thecontact is higher), the detection of those gestures does not requirethat the contacts reach a particular intensity threshold so long as thecriteria for recognizing the gesture can be met in circumstances wherethe contact does not reach the particular intensity threshold (e.g.,even if the amount of time that it takes to recognize the gesturechanges).

Contact intensity thresholds, duration thresholds, and movementthresholds are, in some circumstances, combined in a variety ofdifferent combinations in order to create heuristics for distinguishingtwo or more different gestures directed to the same input element orregion so that multiple different interactions with the same inputelement are enabled to provide a richer set of user interactions andresponses. The statement that a particular set of gesture recognitioncriteria do not require that the intensity of the contact(s) meet arespective intensity threshold in order for the particular gesturerecognition criteria to be met does not preclude the concurrentevaluation of other intensity-dependent gesture recognition criteria toidentify other gestures that do have a criteria that is met when agesture includes a contact with an intensity above the respectiveintensity threshold. For example, in some circumstances, first gesturerecognition criteria for a first gesture—which do not require that theintensity of the contact(s) meet a respective intensity threshold inorder for the first gesture recognition criteria to be met—are incompetition with second gesture recognition criteria for a secondgesture—which are dependent on the contact(s) reaching the respectiveintensity threshold. In such competitions, the gesture is, optionally,not recognized as meeting the first gesture recognition criteria for thefirst gesture if the second gesture recognition criteria for the secondgesture are met first. For example, if a contact reaches the respectiveintensity threshold before the contact moves by a predefined amount ofmovement, a deep press gesture is detected rather than a swipe gesture.Conversely, if the contact moves by the predefined amount of movementbefore the contact reaches the respective intensity threshold, a swipegesture is detected rather than a deep press gesture. Even in suchcircumstances, the first gesture recognition criteria for the firstgesture still do not require that the intensity of the contact(s) meet arespective intensity threshold in order for the first gesturerecognition criteria to be met because if the contact stayed below therespective intensity threshold until an end of the gesture (e.g., aswipe gesture with a contact that does not increase to an intensityabove the respective intensity threshold), the gesture would have beenrecognized by the first gesture recognition criteria as a swipe gesture.As such, particular gesture recognition criteria that do not requirethat the intensity of the contact(s) meet a respective intensitythreshold in order for the particular gesture recognition criteria to bemet will (A) in some circumstances ignore the intensity of the contactwith respect to the intensity threshold (e.g. for a tap gesture) and/or(B) in some circumstances still be dependent on the intensity of thecontact with respect to the intensity threshold in the sense that theparticular gesture recognition criteria (e.g., for a long press gesture)will fail if a competing set of intensity-dependent gesture recognitioncriteria (e.g., for a deep press gesture) recognize an input ascorresponding to an intensity-dependent gesture before the particulargesture recognition criteria recognize a gesture corresponding to theinput (e.g., for a long press gesture that is competing with a deeppress gesture for recognition).

Graphics module 132 includes various known software components forrendering and displaying graphics on touch-sensitive display system 112or other display, including components for changing the visual impact(e.g., brightness, transparency, saturation, contrast or other visualproperty) of graphics that are displayed. As used herein, the term“graphics” includes any object that can be displayed to a user,including without limitation text, web pages, icons (such asuser-interface objects including soft keys), digital images, videos,animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions (e.g., instructions used by haptic feedbackcontroller 161) to produce tactile outputs using tactile outputgenerator(s) 167 at one or more locations on device 100 in response touser interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weathermini applications, local yellow page mini applications, andmap/navigation mini applications).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   mini application modules 149, which optionally include one or        more of: weather mini application 149-1, stocks mini application        149-2, calculator mini application 149-3, alarm clock mini        application 149-4, dictionary mini application 149-5, and other        mini applications obtained by the user, as well as user-created        mini applications 149-6;    -   mini application creator module 150 for making user-created mini        applications 149-6;    -   search module 151;    -   video and music player module 152, which is, optionally, made up        of a video player module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, contacts module 137 includes executable instructions tomanage an address book or contact list (e.g., stored in applicationinternal state 192 of contacts module 137 in memory 102 or memory 370),including: adding name(s) to the address book; deleting name(s) from theaddress book; associating telephone number(s), e-mail address(es),physical address(es) or other information with a name; associating animage with a name; categorizing and sorting names; providing telephonenumbers and/or e-mail addresses to initiate and/or facilitatecommunications by telephone 138, video conference 139, e-mail 140, or IM141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, contact module 130, graphics module 132, and text input module 134,telephone module 138 includes executable instructions to enter asequence of characters corresponding to a telephone number, access oneor more telephone numbers in address book 137, modify a telephone numberthat has been entered, dial a respective telephone number, conduct aconversation and disconnect or hang up when the conversation iscompleted. As noted above, the wireless communication optionally usesany of a plurality of communications standards, protocols andtechnologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, optical sensor(s) 164, optical sensor controller 158, contactmodule 130, graphics module 132, text input module 134, contact list137, and telephone module 138, videoconferencing module 139 includesexecutable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants inaccordance with user instructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, the instant messaging module 141 includesexecutable instructions to enter a sequence of characters correspondingto an instant message, to modify previously entered characters, totransmit a respective instant message (for example, using a ShortMessage Service (SMS) or Multimedia Message Service (MMS) protocol fortelephony-based instant messages or using XMPP, SIMPLE, Apple PushNotification Service (APNs) or IMPS for Internet-based instantmessages), to receive instant messages, and to view received instantmessages. In some embodiments, transmitted and/or received instantmessages optionally include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs,or IMPS).

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,text input module 134, GPS module 135, map module 154, and video andmusic player module 152, workout support module 142 includes executableinstructions to create workouts (e.g., with time, distance, and/orcalorie burning goals); communicate with workout sensors (in sportsdevices and smart watches); receive workout sensor data; calibratesensors used to monitor a workout; select and play music for a workout;and display, store and transmit workout data.

In conjunction with touch-sensitive display system 112, displaycontroller 156, optical sensor(s) 164, optical sensor controller 158,contact module 130, graphics module 132, and image management module144, camera module 143 includes executable instructions to capture stillimages or video (including a video stream) and store them into memory102, modify characteristics of a still image or video, and/or delete astill image or video from memory 102.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, and camera module 143, image management module 144 includesexecutable instructions to arrange, modify (e.g., edit), or otherwisemanipulate, label, delete, present (e.g., in a digital slide show oralbum), and store still and/or video images.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, and text input module 134, browser module 147 includes executableinstructions to browse the Internet in accordance with userinstructions, including searching, linking to, receiving, and displayingweb pages or portions thereof, as well as attachments and other fileslinked to web pages.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, e-mail client module 140, and browser module147, calendar module 148 includes executable instructions to create,display, modify, and store calendars and data associated with calendars(e.g., calendar entries, to do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, mini applicationmodules 149 are mini-applications that are, optionally, downloaded andused by a user (e.g., weather mini application 149-1, stocks miniapplication 149-2, calculator mini application 149-3, alarm clock miniapplication 149-4, and dictionary mini application 149-5) or created bythe user (e.g., user-created mini application 149-6). In someembodiments, a mini application includes an HTML (Hypertext MarkupLanguage) file, a CSS (Cascading Style Sheets) file, and a JavaScriptfile. In some embodiments, a mini application includes an XML(Extensible Markup Language) file and a JavaScript file (e.g., Yahoo!Mini applications).

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, the mini applicationcreator module 150 includes executable instructions to create miniapplications (e.g., turning a user-specified portion of a web page intoa mini application).

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, search module 151 includes executable instructions to searchfor text, music, sound, image, video, and/or other files in memory 102that match one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, and browser module 147, video andmusic player module 152 includes executable instructions that allow theuser to download and play back recorded music and other sound filesstored in one or more file formats, such as MP3 or AAC files, andexecutable instructions to display, present or otherwise play backvideos (e.g., on touch-sensitive display system 112, or on an externaldisplay connected wirelessly or via external port 124). In someembodiments, device 100 optionally includes the functionality of an MP3player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, notes module 153 includes executable instructions to createand manage notes, to do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, GPS module 135, and browser module 147, mapmodule 154 includes executable instructions to receive, display, modify,and store maps and data associated with maps (e.g., driving directions;data on stores and other points of interest at or near a particularlocation; and other location-based data) in accordance with userinstructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesexecutable instructions that allow the user to access, browse, receive(e.g., by streaming and/or download), play back (e.g., on the touchscreen 112, or on an external display connected wirelessly or viaexternal port 124), send an e-mail with a link to a particular onlinevideo, and otherwise manage online videos in one or more file formats,such as H.264. In some embodiments, instant messaging module 141, ratherthan e-mail client module 140, is used to send a link to a particularonline video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating example components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 136, 137-155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay system 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display system 112, as part of amulti-touch gesture). Peripherals interface 118 transmits information itreceives from I/O subsystem 106 or a sensor, such as proximity sensor166, accelerometer(s) 168, and/or microphone 113 (through audiocircuitry 110). Information that peripherals interface 118 receives fromI/O subsystem 106 includes information from touch-sensitive displaysystem 112 or a touch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch-sensitive display system 112 displays more than one view.Views are made up of controls and other elements that a user can see onthe display.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177 or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay system 112, and lift-off of the touch (touch end). In someembodiments, the event also includes information for one or moreassociated event handlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display system 112, when a touch is detected ontouch-sensitive display system 112, event comparator 184 performs a hittest to determine which of the three user-interface objects isassociated with the touch (sub-event). If each displayed object isassociated with a respective event handler 190, the event comparatoruses the result of the hit test to determine which event handler 190should be activated. For example, event comparator 184 selects an eventhandler associated with the sub-event and the object triggering the hittest.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoand music player module 152. In some embodiments, object updater 177creates and updates objects used in application 136-1. For example,object updater 177 creates a new user-interface object or updates theposition of a user-interface object. GUI updater 178 updates the GUI.For example, GUI updater 178 prepares display information and sends itto graphics module 132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 1C is a block diagram illustrating a tactile output module inaccordance with some embodiments. In some embodiments, I/O subsystem 106(e.g., haptic feedback controller 161 (FIG. 1A) and/or other inputcontroller(s) 160 (FIG. 1A)) includes at least some of the examplecomponents shown in FIG. 1C. In some embodiments, peripherals interface118 includes at least some of the example components shown in FIG. 1C.

In some embodiments, the tactile output module includes haptic feedbackmodule 133. In some embodiments, haptic feedback module 133 aggregatesand combines tactile outputs for user interface feedback from softwareapplications on the electronic device (e.g., feedback that is responsiveto user inputs that correspond to displayed user interfaces and alertsand other notifications that indicate the performance of operations oroccurrence of events in user interfaces of the electronic device).Haptic feedback module 133 includes one or more of: waveform module 123(for providing waveforms used for generating tactile outputs), mixer 125(for mixing waveforms, such as waveforms in different channels),compressor 127 (for reducing or compressing a dynamic range of thewaveforms), low-pass filter 129 (for filtering out high frequency signalcomponents in the waveforms), and thermal controller 131 (for adjustingthe waveforms in accordance with thermal conditions). In someembodiments, haptic feedback module 133 is included in haptic feedbackcontroller 161 (FIG. 1A). In some embodiments, a separate unit of hapticfeedback module 133 (or a separate implementation of haptic feedbackmodule 133) is also included in an audio controller (e.g., audiocircuitry 110, FIG. 1A) and used for generating audio signals. In someembodiments, a single haptic feedback module 133 is used for generatingaudio signals and generating waveforms for tactile outputs.

In some embodiments, haptic feedback module 133 also includes triggermodule 121 (e.g., a software application, operating system, or othersoftware module that determines a tactile output is to be generated andinitiates the process for generating the corresponding tactile output).In some embodiments, trigger module 121 generates trigger signals forinitiating generation of waveforms (e.g., by waveform module 123). Forexample, trigger module 121 generates trigger signals based on presettiming criteria. In some embodiments, trigger module 121 receivestrigger signals from outside haptic feedback module 133 (e.g., in someembodiments, haptic feedback module 133 receives trigger signals fromhardware input processing module 146 located outside haptic feedbackmodule 133) and relays the trigger signals to other components withinhaptic feedback module 133 (e.g., waveform module 123) or softwareapplications that trigger operations (e.g., with trigger module 121)based on activation of a user interface element (e.g., an applicationicon or an affordance within an application) or a hardware input device(e.g., a home button or an intensity-sensitive input surface, such as anintensity-sensitive touch screen). In some embodiments, trigger module121 also receives tactile feedback generation instructions (e.g., fromhaptic feedback module 133, FIGS. 1A and 3). In some embodiments,trigger module 121 generates trigger signals in response to hapticfeedback module 133 (or trigger module 121 in haptic feedback module133) receiving tactile feedback instructions (e.g., from haptic feedbackmodule 133, FIGS. 1A and 3).

Waveform module 123 receives trigger signals (e.g., from trigger module121) as an input, and in response to receiving trigger signals, provideswaveforms for generation of one or more tactile outputs (e.g., waveformsselected from a predefined set of waveforms designated for use bywaveform module 123, such as the waveforms described in greater detailbelow with reference to FIGS. 4F-4G).

Mixer 125 receives waveforms (e.g., from waveform module 123) as aninput, and mixes together the waveforms. For example, when mixer 125receives two or more waveforms (e.g., a first waveform in a firstchannel and a second waveform that at least partially overlaps with thefirst waveform in a second channel) mixer 125 outputs a combinedwaveform that corresponds to a sum of the two or more waveforms. In someembodiments, mixer 125 also modifies one or more waveforms of the two ormore waveforms to emphasize particular waveform(s) over the rest of thetwo or more waveforms (e.g., by increasing a scale of the particularwaveform(s) and/or decreasing a scale of the rest of the waveforms). Insome circumstances, mixer 125 selects one or more waveforms to removefrom the combined waveform (e.g., the waveform from the oldest source isdropped when there are waveforms from more than three sources that havebeen requested to be output concurrently by tactile output generator167).

Compressor 127 receives waveforms (e.g., a combined waveform from mixer125) as an input, and modifies the waveforms. In some embodiments,compressor 127 reduces the waveforms (e.g., in accordance with physicalspecifications of tactile output generators 167 (FIG. 1A) or 357 (FIG.3)) so that tactile outputs corresponding to the waveforms are reduced.In some embodiments, compressor 127 limits the waveforms, such as byenforcing a predefined maximum amplitude for the waveforms. For example,compressor 127 reduces amplitudes of portions of waveforms that exceed apredefined amplitude threshold while maintaining amplitudes of portionsof waveforms that do not exceed the predefined amplitude threshold. Insome embodiments, compressor 127 reduces a dynamic range of thewaveforms. In some embodiments, compressor 127 dynamically reduces thedynamic range of the waveforms so that the combined waveforms remainwithin performance specifications of the tactile output generator 167(e.g., force and/or moveable mass displacement limits).

Low-pass filter 129 receives waveforms (e.g., compressed waveforms fromcompressor 127) as an input, and filters (e.g., smooths) the waveforms(e.g., removes or reduces high frequency signal components in thewaveforms). For example, in some instances, compressor 127 includes, incompressed waveforms, extraneous signals (e.g., high frequency signalcomponents) that interfere with the generation of tactile outputs and/orexceed performance specifications of tactile output generator 167 whenthe tactile outputs are generated in accordance with the compressedwaveforms. Low-pass filter 129 reduces or removes such extraneoussignals in the waveforms.

Thermal controller 131 receives waveforms (e.g., filtered waveforms fromlow-pass filter 129) as an input, and adjusts the waveforms inaccordance with thermal conditions of device 100 (e.g., based oninternal temperatures detected within device 100, such as thetemperature of haptic feedback controller 161, and/or externaltemperatures detected by device 100). For example, in some cases, theoutput of haptic feedback controller 161 varies depending on thetemperature (e.g. haptic feedback controller 161, in response toreceiving same waveforms, generates a first tactile output when hapticfeedback controller 161 is at a first temperature and generates a secondtactile output when haptic feedback controller 161 is at a secondtemperature that is distinct from the first temperature). For example,the magnitude (or the amplitude) of the tactile outputs may varydepending on the temperature. To reduce the effect of the temperaturevariations, the waveforms are modified (e.g., an amplitude of thewaveforms is increased or decreased based on the temperature).

In some embodiments, haptic feedback module 133 (e.g., trigger module121) is coupled to hardware input processing module 146. In someembodiments, other input controller(s) 160 in FIG. 1A includes hardwareinput processing module 146. In some embodiments, hardware inputprocessing module 146 receives inputs from hardware input device 145(e.g., other input or control devices 116 in FIG. 1A, such as a homebutton or an intensity-sensitive input surface, such as anintensity-sensitive touch screen). In some embodiments, hardware inputdevice 145 is any input device described herein, such as touch-sensitivedisplay system 112 (FIG. 1A), keyboard/mouse 350 (FIG. 3), touchpad 355(FIG. 3), one of other input or control devices 116 (FIG. 1A), or anintensity-sensitive home button. In some embodiments, hardware inputdevice 145 consists of an intensity-sensitive home button, and nottouch-sensitive display system 112 (FIG. 1A), keyboard/mouse 350 (FIG.3), or touchpad 355 (FIG. 3). In some embodiments, in response to inputsfrom hardware input device 145 (e.g., an intensity-sensitive home buttonor a touch screen), hardware input processing module 146 provides one ormore trigger signals to haptic feedback module 133 to indicate that auser input satisfying predefined input criteria, such as an inputcorresponding to a “click” of a home button (e.g., a “down click” or an“up click”), has been detected. In some embodiments, haptic feedbackmodule 133 provides waveforms that correspond to the “click” of a homebutton in response to the input corresponding to the “click” of a homebutton, simulating a haptic feedback of pressing a physical home button.

In some embodiments, the tactile output module includes haptic feedbackcontroller 161 (e.g., haptic feedback controller 161 in FIG. 1A), whichcontrols the generation of tactile outputs. In some embodiments, hapticfeedback controller 161 is coupled to a plurality of tactile outputgenerators, and selects one or more tactile output generators of theplurality of tactile output generators and sends waveforms to theselected one or more tactile output generators for generating tactileoutputs. In some embodiments, haptic feedback controller 161 coordinatestactile output requests that correspond to activation of hardware inputdevice 145 and tactile output requests that correspond to softwareevents (e.g., tactile output requests from haptic feedback module 133)and modifies one or more waveforms of the two or more waveforms toemphasize particular waveform(s) over the rest of the two or morewaveforms (e.g., by increasing a scale of the particular waveform(s)and/or decreasing a scale of the rest of the waveforms, such as toprioritize tactile outputs that correspond to activations of hardwareinput device 145 over tactile outputs that correspond to softwareevents).

In some embodiments, as shown in FIG. 1C, an output of haptic feedbackcontroller 161 is coupled to audio circuitry of device 100 (e.g., audiocircuitry 110, FIG. 1A), and provides audio signals to audio circuitryof device 100. In some embodiments, haptic feedback controller 161provides both waveforms used for generating tactile outputs and audiosignals used for providing audio outputs in conjunction with generationof the tactile outputs. In some embodiments, haptic feedback controller161 modifies audio signals and/or waveforms (used for generating tactileoutputs) so that the audio outputs and the tactile outputs aresynchronized (e.g., by delaying the audio signals and/or waveforms). Insome embodiments, haptic feedback controller 161 includes adigital-to-analog converter used for converting digital waveforms intoanalog signals, which are received by amplifier 163 and/or tactileoutput generator 167.

In some embodiments, the tactile output module includes amplifier 163.In some embodiments, amplifier 163 receives waveforms (e.g., from hapticfeedback controller 161) and amplifies the waveforms prior to sendingthe amplified waveforms to tactile output generator 167 (e.g., any oftactile output generators 167 (FIG. 1A) or 357 (FIG. 3)). For example,amplifier 163 amplifies the received waveforms to signal levels that arein accordance with physical specifications of tactile output generator167 (e.g., to a voltage and/or a current required by tactile outputgenerator 167 for generating tactile outputs so that the signals sent totactile output generator 167 produce tactile outputs that correspond tothe waveforms received from haptic feedback controller 161) and sendsthe amplified waveforms to tactile output generator 167. In response,tactile output generator 167 generates tactile outputs (e.g., byshifting a moveable mass back and forth in one or more dimensionsrelative to a neutral position of the moveable mass).

In some embodiments, the tactile output module includes sensor 169,which is coupled to tactile output generator 167. Sensor 169 detectsstates or state changes (e.g., mechanical position, physicaldisplacement, and/or movement) of tactile output generator 167 or one ormore components of tactile output generator 167 (e.g., one or moremoving parts, such as a membrane, used to generate tactile outputs). Insome embodiments, sensor 169 is a magnetic field sensor (e.g., a Halleffect sensor) or other displacement and/or movement sensor. In someembodiments, sensor 169 provides information (e.g., a position, adisplacement, and/or a movement of one or more parts in tactile outputgenerator 167) to haptic feedback controller 161 and, in accordance withthe information provided by sensor 169 about the state of tactile outputgenerator 167, haptic feedback controller 161 adjusts the waveformsoutput from haptic feedback controller 161 (e.g., waveforms sent totactile output generator 167, optionally via amplifier 163).

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen (e.g., touch-sensitive display system 112, FIG. 1A) in accordancewith some embodiments. The touch screen optionally displays one or moregraphics within user interface (UI) 200. In these embodiments, as wellas others described below, a user is enabled to select one or more ofthe graphics by making a gesture on the graphics, for example, with oneor more fingers 202 (not drawn to scale in the figure) or one or morestyluses 203 (not drawn to scale in the figure). In some embodiments,selection of one or more graphics occurs when the user breaks contactwith the one or more graphics. In some embodiments, the gestureoptionally includes one or more taps, one or more swipes (from left toright, right to left, upward and/or downward) and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 100. In some implementations orcircumstances, inadvertent contact with a graphic does not select thegraphic. For example, a swipe gesture that sweeps over an applicationicon optionally does not select the corresponding application when thegesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, suchas “home” or menu button 204. As described previously, menu button 204is, optionally, used to navigate to any application 136 in a set ofapplications that are, optionally executed on device 100. Alternatively,in some embodiments, the menu button is implemented as a soft key in aGUI displayed on the touch-screen display.

In some embodiments, device 100 includes the touch-screen display, menubutton 204 (sometimes called home button 204), push button 206 forpowering the device on/off and locking the device, volume adjustmentbutton(s) 208, Subscriber Identity Module (SIM) card slot 210, head setjack 212, and docking/charging external port 124. Push button 206 is,optionally, used to turn the power on/off on the device by depressingthe button and holding the button in the depressed state for apredefined time interval; to lock the device by depressing the buttonand releasing the button before the predefined time interval haselapsed; and/or to unlock the device or initiate an unlock process. Insome embodiments, device 100 also accepts verbal input for activation ordeactivation of some functions through microphone 113. Device 100 also,optionally, includes one or more contact intensity sensors 165 fordetecting intensities of contacts on touch-sensitive display system 112and/or one or more tactile output generators 167 for generating tactileoutputs for a user of device 100.

FIG. 3 is a block diagram of an example multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch-screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above identified elements in FIG. 3 are, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules are, optionally, combined or otherwisere-arranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”)that are, optionally, implemented on portable multifunction device 100.

FIG. 4A illustrates an example user interface for a menu of applicationson portable multifunction device 100 in accordance with someembodiments. Similar user interfaces are, optionally, implemented ondevice 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) for wireless communication(s), such        as cellular and Wi-Fi signals;    -   Time;    -   a Bluetooth indicator;    -   a Battery status indicator;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, labeled            “Music;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks mini application 149-2, labeled            “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather mini application 149-1, labeled            “Weather;”        -   Icon 440 for alarm clock mini application 149-4, labeled            “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, which            provides access to settings for device 100 and its various            applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely examples. For example, other labels are, optionally, used forvarious application icons. In some embodiments, a label for a respectiveapplication icon includes a name of an application corresponding to therespective application icon. In some embodiments, a label for aparticular application icon is distinct from a name of an applicationcorresponding to the particular application icon.

FIG. 4B illustrates an example user interface on a device (e.g., device300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet ortouchpad 355, FIG. 3) that is separate from the display 450. Althoughmany of the examples that follow will be given with reference to inputson touch screen display 112 (where the touch sensitive surface and thedisplay are combined), in some embodiments, the device detects inputs ona touch-sensitive surface that is separate from the display, as shown inFIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 inFIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) that corresponds to aprimary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). Inaccordance with these embodiments, the device detects contacts (e.g.,460 and 462 in FIG. 4B) with the touch-sensitive surface 451 atlocations that correspond to respective locations on the display (e.g.,in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In thisway, user inputs (e.g., contacts 460 and 462, and movements thereof)detected by the device on the touch-sensitive surface (e.g., 451 in FIG.4B) are used by the device to manipulate the user interface on thedisplay (e.g., 450 in FIG. 4B) of the multifunction device when thetouch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures, etc.), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or a stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector,” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch-screen display(e.g., touch-sensitive display system 112 in FIG. 1A or the touch screenin FIG. 4A) that enables direct interaction with user interface elementson the touch-screen display, a detected contact on the touch-screen actsas a “focus selector,” so that when an input (e.g., a press input by thecontact) is detected on the touch-screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch-screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch-screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact or a styluscontact) on the touch-sensitive surface, or to a substitute (proxy) forthe force or pressure of a contact on the touch-sensitive surface. Theintensity of a contact has a range of values that includes at least fourdistinct values and more typically includes hundreds of distinct values(e.g., at least 256). Intensity of a contact is, optionally, determined(or measured) using various approaches and various sensors orcombinations of sensors. For example, one or more force sensorsunderneath or adjacent to the touch-sensitive surface are, optionally,used to measure force at various points on the touch-sensitive surface.In some implementations, force measurements from multiple force sensorsare combined (e.g., a weighted average or a sum) to determine anestimated force of a contact. Similarly, a pressure-sensitive tip of astylus is, optionally, used to determine a pressure of the stylus on thetouch-sensitive surface. Alternatively, the size of the contact areadetected on the touch-sensitive surface and/or changes thereto, thecapacitance of the touch-sensitive surface proximate to the contactand/or changes thereto, and/or the resistance of the touch-sensitivesurface proximate to the contact and/or changes thereto are, optionally,used as a substitute for the force or pressure of the contact on thetouch-sensitive surface. In some implementations, the substitutemeasurements for contact force or pressure are used directly todetermine whether an intensity threshold has been exceeded (e.g., theintensity threshold is described in units corresponding to thesubstitute measurements). In some implementations, the substitutemeasurements for contact force or pressure are converted to an estimatedforce or pressure and the estimated force or pressure is used todetermine whether an intensity threshold has been exceeded (e.g., theintensity threshold is a pressure threshold measured in units ofpressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be readily accessible by the user on a reduced-size devicewith limited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch-screen display can be set to any of alarge range of predefined thresholds values without changing thetrackpad or touch-screen display hardware. Additionally, in someimplementations a user of the device is provided with software settingsfor adjusting one or more of the set of intensity thresholds (e.g., byadjusting individual intensity thresholds and/or by adjusting aplurality of intensity thresholds at once with a system-level click“intensity” parameter).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, a value produced by low-pass filtering theintensity of the contact over a predefined period or starting at apredefined time, or the like. In some embodiments, the duration of thecontact is used in determining the characteristic intensity (e.g., whenthe characteristic intensity is an average of the intensity of thecontact over time). In some embodiments, the characteristic intensity iscompared to a set of one or more intensity thresholds to determinewhether an operation has been performed by a user. For example, the setof one or more intensity thresholds may include a first intensitythreshold and a second intensity threshold. In this example, a contactwith a characteristic intensity that does not exceed the first intensitythreshold results in a first operation, a contact with a characteristicintensity that exceeds the first intensity threshold and does not exceedthe second intensity threshold results in a second operation, and acontact with a characteristic intensity that exceeds the secondintensity threshold results in a third operation. In some embodiments, acomparison between the characteristic intensity and one or moreintensity thresholds is used to determine whether or not to perform oneor more operations (e.g., whether to perform a respective option orforgo performing the respective operation) rather than being used todetermine whether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location (e.g.,a drag gesture), at which point the intensity of the contact increases.In this example, the characteristic intensity of the contact at the endlocation may be based on only a portion of the continuous swipe contact,and not the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmmay be applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The user interface figures described herein optionally include variousintensity diagrams that show the current intensity of the contact on thetouch-sensitive surface relative to one or more intensity thresholds(e.g., a contact detection intensity threshold IT₀, a light pressintensity threshold IT_(L), a deep press intensity threshold IT_(D)(e.g., that is at least initially higher than IT_(L)), and/or one ormore other intensity thresholds (e.g., an intensity threshold IT_(H)that is lower than IT_(L))). This intensity diagram is typically notpart of the displayed user interface, but is provided to aid in theinterpretation of the figures. In some embodiments, the light pressintensity threshold corresponds to an intensity at which the device willperform operations typically associated with clicking a button of aphysical mouse or a trackpad. In some embodiments, the deep pressintensity threshold corresponds to an intensity at which the device willperform operations that are different from operations typicallyassociated with clicking a button of a physical mouse or a trackpad. Insome embodiments, when a contact is detected with a characteristicintensity below the light press intensity threshold (e.g., and above anominal contact-detection intensity threshold IT₀ below which thecontact is no longer detected), the device will move a focus selector inaccordance with movement of the contact on the touch-sensitive surfacewithout performing an operation associated with the light pressintensity threshold or the deep press intensity threshold. Generally,unless otherwise stated, these intensity thresholds are consistentbetween different sets of user interface figures.

In some embodiments, the response of the device to inputs detected bythe device depends on criteria based on the contact intensity during theinput. For example, for some “light press” inputs, the intensity of acontact exceeding a first intensity threshold during the input triggersa first response. In some embodiments, the response of the device toinputs detected by the device depends on criteria that include both thecontact intensity during the input and time-based criteria. For example,for some “deep press” inputs, the intensity of a contact exceeding asecond intensity threshold during the input, greater than the firstintensity threshold for a light press, triggers a second response onlyif a delay time has elapsed between meeting the first intensitythreshold and meeting the second intensity threshold. This delay time istypically less than 200 ms (milliseconds) in duration (e.g., 40, 100, or120 ms, depending on the magnitude of the second intensity threshold,with the delay time increasing as the second intensity thresholdincreases). This delay time helps to avoid accidental recognition ofdeep press inputs. As another example, for some “deep press” inputs,there is a reduced-sensitivity time period that occurs after the time atwhich the first intensity threshold is met. During thereduced-sensitivity time period, the second intensity threshold isincreased. This temporary increase in the second intensity thresholdalso helps to avoid accidental deep press inputs. For other deep pressinputs, the response to detection of a deep press input does not dependon time-based criteria.

In some embodiments, one or more of the input intensity thresholdsand/or the corresponding outputs vary based on one or more factors, suchas user settings, contact motion, input timing, application running,rate at which the intensity is applied, number of concurrent inputs,user history, environmental factors (e.g., ambient noise), focusselector position, and the like. Example factors are described in U.S.Patent application Ser. Nos. 14/399,606 and 14/624,296, which areincorporated by reference herein in their entireties.

For example, FIG. 4C illustrates a dynamic intensity threshold 480 thatchanges over time based in part on the intensity of touch input 476 overtime. Dynamic intensity threshold 480 is a sum of two components, firstcomponent 474 that decays over time after a predefined delay time p1from when touch input 476 is initially detected, and second component478 that trails the intensity of touch input 476 over time. The initialhigh intensity threshold of first component 474 reduces accidentaltriggering of a “deep press” response, while still allowing an immediate“deep press” response if touch input 476 provides sufficient intensity.Second component 478 reduces unintentional triggering of a “deep press”response by gradual intensity fluctuations of in a touch input. In someembodiments, when touch input 476 satisfies dynamic intensity threshold480 (e.g., at point 481 in FIG. 4C), the “deep press” response istriggered.

FIG. 4D illustrates another dynamic intensity threshold 486 (e.g.,intensity threshold I_(D)). FIG. 4D also illustrates two other intensitythresholds: a first intensity threshold I_(H) and a second intensitythreshold I_(L). In FIG. 4D, although touch input 484 satisfies thefirst intensity threshold I_(H) and the second intensity threshold I_(L)prior to time p2, no response is provided until delay time p2 haselapsed at time 482. Also in FIG. 4D, dynamic intensity threshold 486decays over time, with the decay starting at time 488 after a predefineddelay time p1 has elapsed from time 482 (when the response associatedwith the second intensity threshold I_(L) was triggered). This type ofdynamic intensity threshold reduces accidental triggering of a responseassociated with the dynamic intensity threshold I_(D) immediately after,or concurrently with, triggering a response associated with a lowerintensity threshold, such as the first intensity threshold I_(H) or thesecond intensity threshold I_(L).

FIG. 4E illustrate yet another dynamic intensity threshold 492 (e.g.,intensity threshold I_(D)). In FIG. 4E, a response associated with theintensity threshold I_(L) is triggered after the delay time p2 haselapsed from when touch input 490 is initially detected. Concurrently,dynamic intensity threshold 492 decays after the predefined delay timep1 has elapsed from when touch input 490 is initially detected. So adecrease in intensity of touch input 490 after triggering the responseassociated with the intensity threshold I_(L), followed by an increasein the intensity of touch input 490, without releasing touch input 490,can trigger a response associated with the intensity threshold I_(D)(e.g., at time 494) even when the intensity of touch input 490 is belowanother intensity threshold, for example, the intensity threshold I_(L).

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold IT_(L) to an intensity betweenthe light press intensity threshold IT_(L) and the deep press intensitythreshold IT_(D) is sometimes referred to as a “light press” input. Anincrease of characteristic intensity of the contact from an intensitybelow the deep press intensity threshold IT_(D) to an intensity abovethe deep press intensity threshold IT_(D) is sometimes referred to as a“deep press” input. An increase of characteristic intensity of thecontact from an intensity below the contact-detection intensitythreshold IT₀ to an intensity between the contact-detection intensitythreshold IT₀ and the light press intensity threshold IT_(L) issometimes referred to as detecting the contact on the touch-surface. Adecrease of characteristic intensity of the contact from an intensityabove the contact-detection intensity threshold IT₀ to an intensitybelow the contact-detection intensity threshold IT₀ is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments IT₀ is zero. In some embodiments, IT₀ is greaterthan zero. In some illustrations a shaded circle or oval is used torepresent intensity of a contact on the touch-sensitive surface. In someillustrations, a circle or oval without shading is used represent arespective contact on the touch-sensitive surface without specifying theintensity of the respective contact.

In some embodiments, described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., the respective operation is performed on a“down stroke” of the respective press input). In some embodiments, thepress input includes an increase in intensity of the respective contactabove the press-input intensity threshold and a subsequent decrease inintensity of the contact below the press-input intensity threshold, andthe respective operation is performed in response to detecting thesubsequent decrease in intensity of the respective contact below thepress-input threshold (e.g., the respective operation is performed on an“up stroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., the respective operationis performed on an “up stroke” of the respective press input).Similarly, in some embodiments, the press input is detected only whenthe device detects an increase in intensity of the contact from anintensity at or below the hysteresis intensity threshold to an intensityat or above the press-input intensity threshold and, optionally, asubsequent decrease in intensity of the contact to an intensity at orbelow the hysteresis intensity, and the respective operation isperformed in response to detecting the press input (e.g., the increasein intensity of the contact or the decrease in intensity of the contact,depending on the circumstances).

For ease of explanation, the description of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting: an increase in intensityof a contact above the press-input intensity threshold, an increase inintensity of a contact from an intensity below the hysteresis intensitythreshold to an intensity above the press-input intensity threshold, adecrease in intensity of the contact below the press-input intensitythreshold, or a decrease in intensity of the contact below thehysteresis intensity threshold corresponding to the press-inputintensity threshold. Additionally, in examples where an operation isdescribed as being performed in response to detecting a decrease inintensity of a contact below the press-input intensity threshold, theoperation is, optionally, performed in response to detecting a decreasein intensity of the contact below a hysteresis intensity thresholdcorresponding to, and lower than, the press-input intensity threshold.As described above, in some embodiments, the triggering of theseresponses also depends on time-based criteria being met (e.g., a delaytime has elapsed between a first intensity threshold being met and asecond intensity threshold being met).

User Interfaces and Associated Processes

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on an electronicdevice, such as portable multifunction device 100 or device 300, with adisplay, a touch-sensitive surface, (optionally) one or more tactileoutput generators for generating tactile outputs, and (optionally) oneor more sensors to detect intensities of contacts with thetouch-sensitive surface.

FIGS. 5A-5AZ illustrate example user interfaces for clearing sets ofnotifications in accordance with some embodiments. The user interfacesin these figures are used to illustrate the processes described below,including the processes in FIGS. 6A-6G. For convenience of explanation,some of the embodiments will be discussed with reference to operationsperformed on a device with a touch-sensitive display system 112. In suchembodiments, the focus selector is, optionally: a respective finger orstylus contact, a representative point corresponding to a finger orstylus contact (e.g., a centroid of a respective contact or a pointassociated with a respective contact), or a centroid of two or morecontacts detected on the touch-sensitive display system 112. However,analogous operations are, optionally, performed on a device with adisplay 450 and a separate touch- sensitive surface 451 in response todetecting the contacts on the touch-sensitive surface 451 whiledisplaying the user interfaces shown in the figures on the display 450,along with a focus selector.

FIGS. 5A1 to 5A4 illustrate activation of a display (e.g.,touch-sensitive display 112) in response to changing an orientation ofdevice 100. When the display has been activated, notifications that werereceived while the device was in a screen-off state were received. Thesenotifications are displayed when the device transitions to a screen-onstate. In some embodiments, the device uses one or more sensors (e.g.,accelerometer, gyro, audio sensor, heat sensor, and/or light sensor) todetermine whether an orientation of the device has changed. For example,the device determines whether the device has been rotated by more than athreshold angle (e.g., rotated along an axis of the device, such astilted from a position in which the device is substantially horizontalto a position in which the device is substantially vertical). In FIG.5A1, the device is in a screen-off state while it is held flat in auser's hand 502, such that the device display is substantiallyhorizontal. In FIG. 5A2, the device is tilted such that the display ismore vertical than in FIG. 5A1. Because a tilt angle of the device hasnot increased above a threshold tilt angle in FIG. 5A2, the display isnot activated. In FIG. 5A3, the device is tilted such that the displayis more vertical than in FIG. 5A2. Because a tilt angle of the devicehas increased above a threshold tilt angle in FIG. 5A3, the display hastransitioned from a screen-off state to a screen-on state and wakescreen user interface 504 is displayed by the display 112. In FIG. 5A4,the display 112 is substantially vertical.

In some embodiments, wake screen user interface 504 is a user interfacethat is displayed when the device transitions from a screen-off state toa screen-on state (e.g., while the device 100 is in a locked state) andwake screen user interface 504 is available to be redisplayed (e.g., toallow a user to view notifications, access a mini application userinterface and/or access a control center user interface, as describedfurther below) after the device is unlocked. In some embodiments, whenwake screen user interface 504 is accessed after the device is unlocked,wake screen user interface 504 is referred to as a cover sheet userinterface. The terms “wake screen user interface” and “cover sheet userinterface” are used interchangeably herein to refer to wake screen userinterface 504.

FIG. 5B illustrates a wake screen user interface 504, in accordance withsome embodiments. Wake screen user interface 504 displays missednotifications 506, 508, 510, and 512 that were received and/or generatedby device 100 (e.g., while device 100 was in a screen-off state).

In some embodiments, the missed notifications that are displayed on thewake screen user interface 504 are cleared individually in response touser interaction with a notification (e.g., when a user accesses anapplication that corresponds to a notification, as illustrated at FIGS.5L-5M, or when a user provides input to delete a notification, asillustrated at FIGS. 5Y-5AC). In some embodiments, a set of all missednotifications are collectively cleared when notification clearancecriteria are satisfied, e.g., when input is received at a time that is(1) after a respective notification of the one or more notifications hasbeen cleared through direct user interaction with the respectivenotification or an application that corresponds to the respectivenotification and (2) after the device has transitioned from thescreen-on state to the screen-off state at least once since the lastdirect user interaction that dismissed a respective notification.

In FIGS. 5B-5D, the device transitions from a screen-on state to ascreen-off state. Since this transition has not occurred after a userinteraction to dismiss a notification, the missed notifications remaindisplayed, as shown in FIG. 5D.

After device 100 transitions from a screen-off state, as shown in FIG.5A, to a screen-on state, as shown in FIG. 5B, the device 100transitions from the screen-on state back to a screen-off state, asshown in FIG. 5C. In some embodiments, a transition from a screen-onstate to a screen-off state (and/or from a screen-off state to ascreen-on state) occurs in response to an input detected at a control(e.g., a push button 206) of device 100. In some embodiments, atransition from a screen-on state to a screen-off state occurs when atime during which no input has been detected by the device increasesbeyond a threshold duration.

In FIG. 5D, the device has transitioned from the screen-off state shownin FIG. 5C back to a screen-on state. Notifications 506, 508, 510, and512 continue to be displayed after the transition from a screen-on state(as shown in FIG. 5B) to a screen-off state (as shown in FIG. 5C) andback to a screen-on state (as shown in FIG. 5D).

In FIGS. 5E-5K, a set of missed notifications remains available on wakescreen user interface 504 after user input is provided to unlock thedevice.

FIG. 5E illustrates an input (e.g., an upward swipe) by a contact ontouch screen 112 that is initiated at a lower edge of touch screen 112,as indicated by focus selector 514. In response to the input, inaccordance with a determination that the device is locked, anauthentication user interface 518 is displayed, as shown in FIG. 5F.

In FIG. 5G, an authentication input (e.g., a tap input) by a contact ontouch screen 112 is detected at a location within authentication userinterface 518, as indicated by focus selector 520. In response to theauthentication input, the device is unlocked and home screen userinterface 522 (e.g., a user interface for a menu of applications asdescribed with regard to FIG. 4A) is displayed, as shown in FIG. 5H.

FIGS. 5I-5J illustrate an input (e.g., a downward swipe) that isinitiated by a contact at an upper edge of touch screen 112, asindicated by focus selector 524. In response to the input, wake screenuser interface 504 slides down from the upper edge of display 112, asshown in FIGS. 5I-5K. As indicated in FIG. 5K, notifications 506, 508,510, and 512 continue to be displayed on the wake screen user interface504 when wake screen user interface 504 is revealed after the device isunlocked and home screen user interface 522 is displayed.

FIGS. 5L-5M illustrate a user interaction with notification 510 thatcauses the notification to be dismissed (as shown in FIG. 5P), whilenotifications 506, 508, and 512 remain displayed on wake screen userinterface 504 (e.g., because no transition from the screen-on state tothe screen-off state has occurred since the user interaction to dismissnotification 510).

In FIG. 5L, an input (e.g., a tap input) by a contact on touch screen112 is detected at a location that corresponds to notification 510, asindicated by focus selector 528. In response to the input, wake screenuser interface 504 ceases to be displayed and an application userinterface (e.g., messages application user interface 530) thatcorresponds to the notification 510 is displayed, as shown in FIG. 5M.

FIGS. 5N-5O illustrate an input (e.g., a downward swipe) that isinitiated by a contact on touch screen 112 at an upper edge of touchscreen 112, as indicated by focus selector 532. In response to theinput, wake screen user interface 504 slides down from the upper edge ofdisplay 112, as shown in FIGS. 5N-5P. As indicated in FIG. 5P, as aresult of the interaction with notification 510 (e.g., the tap input onnotification 510 that caused the messages application user interface 530to be displayed) notification 510 is no longer displayed on wake screenuser interface 504. In FIG. 5P, notifications 506, 508, and 512 continueto be displayed on the wake screen user interface 504.

In FIGS. 5Q-5X, after navigation to a first application user interfaceand from the first application user interface to a second applicationuser interface, notifications 506, 508, and 512 continue to be displayed(as shown in FIG. 5X).

FIG. 5Q illustrates an input (e.g., a upward swipe) that is initiated bya contact at a location near the lower edge of touch screen 112, asindicated by focus selector 534. In response to the input, wake screenuser interface 504 slides up from the lower edge of display 112 toredisplay the underlying messages application user interface 530 (thatwas previously covered by wake screen user interface 504), as shown inFIGS. 5Q-5R.

FIG. 5S illustrates an input by a contact on touch screen 112 that isinitiated by a contact at a location near the lower edge of touch screen112, as indicated by focus selector 536. In response to the input,during which the focus selector moves along a path indicated by arrow538, messages application user interface 530 moves along the pathindicated by arrow 538 to reveal web browser application user interface540, as shown in FIGS. 5S-5U.

FIGS. 5V-5W illustrate an input (e.g., a downward swipe) that isinitiated by a contact at a location near the upper edge of touch screen112, as indicated by focus selector 542. In response to the input, wakescreen user interface 504 slides down from the lower edge of display112, as shown in FIGS. 5V-5X.

FIGS. 5Y-5AC illustrate a user interaction with notification 506 thatcauses notification 506 to be dismissed (as shown in FIG. 5AC), whilenotifications 508 and 512 remain displayed on wake screen user interface504 (e.g., because no transition from the screen-on state to thescreen-off state has occurred since the user interaction to dismissnotification 510 and no transition from the screen-on state to thescreen-off state has occurred since the user interaction to dismissnotification 506).

FIGS. 5AD-5AO illustrate user input to access a music application userinterface 560 and to initiate an active playback mode of the musicapplication. While the music application is in an active playback mode,a media banner 568 is displayed on wake screen user interface 504, asshown in FIG. 5AO. FIGS. 5AP-5AU illustrate input to stop mediaplayback. When music application is not in an active playback mode,media banner 568 is no longer displayed on wake screen user interface504, as shown in FIG. 5AU.

FIGS. 5Y-5Z illustrate an input (e.g., a horizontal drag input) by acontact on touch screen 112 at a location that corresponds tonotification 506, as indicated by focus selector 544. In response to theinput, deletion affordance 546 is revealed at a location that isadjacent to notification 506, as shown in FIG. 5Z. In FIG. 5AA, thecontact indicated by focus selector 544 has lifted off of touch screen112.

In FIG. 5AB, an input (e.g., a tap input) is detected at a location thatcorresponds to deletion affordance 546, as indicated by focus selector548. In response to the input, notification 506 ceases to be displayedon wake screen user interface 504, as shown in FIG. 5AC. In FIG. 5AC,notifications 508 and 512 continue to be displayed on the wake screenuser interface 504.

FIGS. 5AD-5AE illustrate an input (e.g., an upward swipe) that isinitiated by a contact at a location near the upper edge of touch screen112, as indicated by focus selector 550. In response to the input, wakescreen user interface 504 slides up from the lower edge of display 112to redisplay the underlying web browser application user interface 540(that was previously covered by wake screen user interface 504), asshown in FIGS. 5AD-5AF.

FIG. 5AG illustrates an input (e.g., an upward swipe) by a contact ontouch screen 112 that is initiated by a contact at location thatcorresponds to home affordance 552, as indicated by focus selector 554.In response to the input, display of web browser application userinterface 540 is replaced by display of home screen user interface 522,as shown in FIGS. 5AG-5AH.

In FIG. 5AI, an input (e.g., a tap input) is detected at a location thatcorresponds to affordance 556 for displaying a music applicationinterface, as indicated by focus selector 558. In response to the input,a music application user interface 552 is displayed, as shown in FIG.5AJ.

In FIG. 5AK, an input (e.g., a tap input) is detected at a location thatcorresponds to media playback control affordance 562, as indicated byfocus selector 564. In response to the input, the music applicationtransitions to an active playback mode (e.g., music playback isinitiated) as shown in FIG. 5AL (e.g., as indicated by the changed stateof media playback control affordance 562).

FIGS. 5AM-5AN illustrate an input (e.g., a downward swipe) that isinitiated by a contact at a location near the upper edge of touch screen112, as indicated by focus selector 566. In response to the input, wakescreen user interface 504 slides down from the upper edge of display112, as shown in FIGS. 5AM-5AO.

Figure AO shows a wake screen user interface 504 that displays a mediabanner 568 that corresponds to the ongoing music playback initiated fromthe music application. As indicated in FIG. 5AP, media banner 568includes media track information 570 and a banner playback controlaffordance 572.

In Figure AP, an input (e.g., a tap input) is detected at a locationthat corresponds to banner playback control affordance 572, as indicatedby focus selector 574. In response to the input, music playback ispaused as shown in FIG. 5AQ (e.g., as indicated by the changed state ofbanner playback control affordance 572).

FIG. 5AR illustrates an input (e.g., a upward swipe) that is initiatedby a contact near the lower edge of touch screen 112, as indicated byfocus selector 576. In response to the input, wake screen user interface504 slides up from the lower edge of display 112 to redisplay theunderlying music user interface 522 (that was previously covered by wakescreen user interface 504), as shown in FIGS. 5AR-5AS.

FIG. 5AT illustrates an input (e.g., a downward swipe) by a contact ontouch screen 112, as indicated by focus selector 578. In response to theinput, wake screen user interface 504 slides down from the upper edge ofdisplay 112, as shown in FIGS. 5AT-5AU.

In FIG. 5AU, media banner 568 is no longer displayed on wake screen userinterface 504 (e.g., because the input to display wake screen userinterface 504 was received while the music application was not in anactive media playback mode).

FIGS. 5AV-5AW illustrate a transition from the screen-on state to thescreen-off state that occurs after the user interaction to dismissnotification 510 (e.g., as described with regard to FIGS. 5L-5P) andafter the user interaction to dismiss notification 606 (as describedwith regard to FIGS. 5Y-5AC). As shown in FIG. 5AW, because notificationclearance criteria are satisfied (e.g., input (to transition the devicefrom the screen-off state to the screen-on state) is received at a timethat is (1) after a respective notification of the one or morenotifications has been cleared through direct user interaction with therespective notification or an application that corresponds to therespective notification and (2) after the device has transitioned fromthe screen-on state to the screen-off state at least once since the lastdirect user interaction that dismissed a respective notification), allnotifications have been cleared from wake screen 504.

In FIG. 5AV, device 100 has transitioned from the screen-on state, asshown in FIG. 5AU, to a screen-off state.

After the screen has transitioned from a screen-off state, as shown inFIG. 5AV, back to a screen-on state, as shown in Figure AW (and afterthe user has interacted with at least one notification, e.g., asdescribed with regard to FIGS. 5L-5P and/or as described with regard toFIGS. 5Y-5AC), wake screen user interface 504 is displayed with nonotifications.

FIGS. 5AW-5AZ illustrate a “rubber band” effect that occurs when aninput by a contact with touch screen 112 (as indicated by focus selector580) drags a time/date indicator 582 downward, and then the time/dateindicator moves back to its original position in response to lift off ofthe contact from the touch sensitive surface. As focus selector 580moves across touch screen 112 along a path indicated by arrow 584,time/date indicator 582 moves in accordance with the movement of thefocus selector 580, as shown in FIGS. 5AW-5AX. When focus selector 580lifts off of touch screen 112, the time/date indicator 582 returns toits original position, as shown in FIGS. 5AY-5AZ.

FIGS. 5BA-5CX illustrate example user interfaces for displayingnotification history, in accordance with some embodiments. The userinterfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIGS. 7A-7E. For convenienceof explanation, some of the embodiments will be discussed with referenceto operations performed on a device with a touch-sensitive displaysystem 112. In such embodiments, the focus selector is, optionally: arespective finger or stylus contact, a representative pointcorresponding to a finger or stylus contact (e.g., a centroid of arespective contact or a point associated with a respective contact), ora centroid of two or more contacts detected on the touch-sensitivedisplay system 112. However, analogous operations are, optionally,performed on a device with a display 450 and a separate touch-sensitivesurface 451 in response to detecting the contacts on the touch-sensitivesurface 451 while displaying the user interfaces shown in the figures onthe display 450, along with a focus selector.

FIG. 5BA displays wake screen user interface 504 (e.g., in response toan event that triggered a transition from a screen-off state to ascreen-on state). Wake screen user interface 504 displays missednotifications 586, 588, 590, and 592.

FIGS. 5BB-5BE illustrate a “rubber band” effect that occurs when aninput by a contact with touch screen 112 (as indicated by focus selector594) drags missed notifications 586, 588, 590, and 592 and time/dateindicator 582 downward, and then the missed notifications 586, 588, 590,and 592 and time/date indicator 582 move back to their originalpositions in response to lift off of the contact from the touchsensitive surface. As focus selector 594 moves across touch screen 112along a path indicated by arrow 596, missed notifications 586, 588, 590,and 592 and time/date indicator 582 move in accordance with the movementof the focus selector 594, as shown in FIGS. 5BB-5BC. When focusselector 594 lifts off of touch screen 112, notifications 586, 588, 590,and 592 and time/date indicator 582 return to their original positions,as shown in FIGS. 5BD-5BE.

FIGS. 5BF-5BG illustrate an input (e.g., an upward swipe) that causesmissed notifications to scroll upwards, but that does not meet criteriafor displaying previously received notifications. In FIG. 5BF, an inputis initiated by a contact with touch screen 112, as indicated by focusselector 598, within a region on wake screen interface 504 (e.g., aregion delineated by dotted line 5100) in which notifications 586-592are displayed. In response to the input, missed notifications 586-592move upward, as shown in FIGS. 5BF-5BG, revealing an additional missednotification 5102 and a previously received notification indicator 5104,as shown in FIG. 5BH.

FIGS. 5BI-5BN illustrate an input that meets criteria for displayingpreviously received notifications. In FIG. 5BI, an input (e.g., anupward swipe) is initiated by a contact with touch screen 112 (e.g., ata location that corresponds to previously received notificationindicator 5102), as indicated by focus selector 5106. In response to theinput, missed notifications 586-592 move upward, as shown in FIGS.5BJ-5BP. As shown in FIG. 5BK, when movement of the focus selector 5106across touch screen 112 has increased above a threshold distance (asindicated by 5108), previously received notification 506 is displayed,and the device generates a tactile output (as indicated at 5112). Afterthe focus selector 5106 moves beyond the threshold distance, additionalpreviously received notifications 508 and 510 are displayed, and thepreviously received notifications 506, 508, and 510 move at a fasterrate than the rate of movement of focus selector 5106 and missednotifications 590, 592 and 5102 (e.g., to provide a visual effect of thepreviously received notifications 506, 508, and 510 “rushing to catchup” with the missed notifications 590, 592 and 5102), as shown in FIGS.5BK-5BM. In FIGS. 5BM-5BN, focus selector 5106 continues to move upwardacross touch screen 112, and previously received notification 512 isrevealed. In FIGS. 5BO-5BP, after the contact indicated by focusselector 5106 has lifted off from touch screen 112, previously receivednotifications 506, 508, 510, and 512 continue to move upward.

FIGS. 5BQ-5BR illustrate an input that displays additional previouslyreceived notifications. In FIG. 5BQ, an input (e.g., an upward swipe) isinitiated by a contact with touch screen 112, as indicated by focusselector 5120, within a region on wake screen interface 504 in whichpreviously received notifications 506-512 are displayed. In response tothe input, previously received notifications 506-512 move upward, asshown in FIGS. 5BQ-5BR. In FIG. 5BR, a second previously receivednotification indicator 5122 (e.g., for notifications received on theprevious day) and a previously received notification 5124 (e.g.,received on the previous day) are displayed on wake screen userinterface 504.

FIGS. 5BS-5BT illustrate an input to redisplay missed notifications. InFIG. 5BS, an input (e.g., a downward swipe) is initiated by a contactwith touch screen 112, as indicated by focus selector 5126, within aregion on wake screen interface 504 in which previously receivednotifications 506-512 and 5124 are displayed. In response to the input,previously received notifications 506-512 and 5124 scroll downwards andmissed notifications 590, 592, and 5102 are redisplayed on wake screenuser interface 504, as shown in FIGS. 5BS-5BU.

FIGS. 5BV-5BZ illustrate a user interaction with notification 592 thatcauses the notification to be dismissed (as shown in FIG. 5BZ), whilemissed notifications other than 592 and previously receivednotifications remain displayed on wake screen user interface 504 (e.g.,because no transition from the screen-on state to the screen-off statehas occurred since the user interaction to dismiss notification 592).

FIGS. 5BV-5BW illustrate an input (e.g., a horizontal drag input) by acontact on touch screen 112 at a location that corresponds tonotification 592, as indicated by focus selector 5128. In response tothe input, deletion affordance 5130 is revealed at a location that isadjacent to notification 592, as shown in FIG. 5BW. In FIG. 5BX, thecontact indicated by focus selector 5130 has lifted off of touch screen112.

In FIG. 5BY, an input (e.g., a tap input) is detected at a location thatcorresponds to deletion affordance 5130, as indicated by focus selector5132. In response to the input, notification 592 ceases to be displayedon wake screen user interface 504, as shown in FIG. 5BZ.

FIG. 5CA illustrates an input that meets criteria for dismissingpreviously dismissed notifications. In response to the input, onlymissed notifications remain displayed on wake screen 504, as shown inFIG. 5CB.

FIGS. 5CA-5CB illustrate an input (e.g., a downward swipe) that isinitiated by a contact with touch screen 112, as indicated by focusselector 5136, within a region on wake screen interface 504 in whichmissed notifications (e.g., 592 and 5102) and/or previously receivednotifications (e.g., 506-510) are displayed. In response to the input,previously received notifications 506-510 scroll downwards and missednotifications 586, 588, 592, and 5102 are redisplayed on wake screenuser interface 504, as shown in FIG. 5CA-5CB.

FIGS. 5CC-5CQ illustrate input for accessing a control center userinterface 5138, a mini application user interface 5140, and a userinterface underlying wake screen user interface (e.g., home screen userinterface 522) from wake screen user interface 504.

FIGS. 5CC-5CD illustrate an input (e.g., a leftward swipe) that isinitiated by a contact on touch screen 112, as indicated by focusselector 5136. In response to the input, wake screen user interface 504slides to the left and control center user interface 5138 is revealed,as shown in FIG. 5CC-5CE.

FIGS. 5CF-5CG illustrate an input (e.g., a rightward swipe) that isinitiated by a contact on touch screen 112, as indicated by focusselector 5142. In response to the input, control center user interface5138 slides to the right and wake screen user interface 504 is revealed,as shown in FIG. 5CF-5CH.

FIGS. 5CI-5CJ illustrate an input (e.g., a rightward swipe) that isinitiated by a contact on touch screen 112, as indicated by focusselector 5144. In response to the input, wake screen user interface 504slides to the right and mini application user interface 5140 isrevealed, as shown in FIG. 5CI-5CK.

FIGS. 5CL-5CM illustrate an input (e.g., a leftward swipe) that isinitiated by a contact on touch screen 112, as indicated by focusselector 5146. In response to the input, mini application user interface5140 slides to the left and wake screen user interface 504 is revealed,as shown in FIG. 5CL-5CN.

FIG. 5CO illustrates an input by a contact on touch screen 112 that isinitiated at a lower edge of touch screen 112, as indicated by focusselector 5146. In response to the input, display of wake screen userinterface 504 is replaced by display of home screen user interface 522,as shown in FIGS. 5CO-5CQ.

FIGS. 5CR-5CS illustrate a transition from the screen-on state to thescreen-off state that occurs after the user interaction to dismissnotification 592 (e.g., as described with regard to FIGS. 5BV-5BZ). Asshown in FIG. 5CS, because notification clearance criteria are satisfied(e.g., input (to transition the device from the screen-off state to thescreen-on state) is received at a time that is (1) after a respectivenotification of the one or more notifications has been cleared throughdirect user interaction with the respective notification or anapplication that corresponds to the respective notification and (2)after the device has transitioned from the screen-on state to thescreen-off state at least once since the last direct user interactionthat dismissed a respective notification), all notifications have beencleared from wake screen 504.

In FIG. 5CR, device 100 has transitioned from the screen-on state, asshown in FIG. 5CQ, to a screen-off state.

After the screen has transitioned from a screen-off state, as shown inFIG. 5CR, back to a screen-on state, as shown in FIG. 5CS (and after theuser has interacted with at least one notification, e.g., as describedwith regard to FIGS. 5BV-5BZ), wake screen user interface 504 isdisplayed with no notifications.

FIGS. 5CS-5CV illustrate a “rubber band” effect that occurs when aninput by a contact with touch screen 112 (as indicated by focus selector5150) drags a time/date indicator 582 downward, and then the time/dateindicator moves back to its original position in response to lift off ofthe contact from the touch sensitive surface.

After all notifications have been cleared, as shown at FIG. 5CS, thecleared notifications can be recalled, as shown at FIGS. 5CW-5CX. FIG.5CW illustrates an input (e.g., an upward swipe) that is initiated by acontact with touch screen 112 at a location on wake screen userinterface 504, as indicated by focus selector 5152. In response to theinput, the notifications that were displayed as missed notifications586-592 and subsequently cleared (as described with regard to FIGS. 5BA,5BV-5BZ, and 5CR-5CS) move upward when movement of the focus selector5152 across touch screen 112 has increased above a threshold distance.In FIG. 5CX, the notifications that were displayed as missednotifications 586-592 are displayed as previously receivednotifications.

FIGS. 5CY-5EB illustrate example user interfaces for displaying updatinginformation from an application in a floating banner, in accordance withsome embodiments. The user interfaces in these figures are used toillustrate the processes described below, including the processes inFIGS. 8A-8C. For convenience of explanation, some of the embodimentswill be discussed with reference to operations performed on a devicewith a touch-sensitive display system 112. In such embodiments, thefocus selector is, optionally: a respective finger or stylus contact, arepresentative point corresponding to a finger or stylus contact (e.g.,a centroid of a respective contact or a point associated with arespective contact), or a centroid of two or more contacts detected onthe touch-sensitive display system 112. However, analogous operationsare, optionally, performed on a device with a display 450 and a separatetouch-sensitive surface 451 in response to detecting the contacts on thetouch-sensitive surface 451 while displaying the user interfaces shownin the figures on the display 450, along with a focus selector.

FIGS. 5CY-5DA illustrate input for activating a navigation mode of amaps application and displaying a navigation banner 5160 thatcorresponds to the active navigation mode of the maps application.

FIG. 5CY shows a maps application user interface 5154 displayed bydisplay 112 of device 100.

In FIG. 5CZ, an input (e.g., a tap input) by a contact on touch screen112 is detected at a location that corresponds to a control 5156 foractivating a navigation mode of the maps application, as indicated byfocus selector 5158. In response to the input, the navigation mode ofthe maps application is initiated, and a navigation mode user interfaceis displayed in maps application user interface 5154, as indicated atFigure DA. A navigation banner 5160 (e.g., that includes navigationdirection text and/or a navigation direction image, such as a directionarrow) is displayed on the navigation mode user interface of the mapsapplication user interface 5154.

In FIGS. 5DB-5DF, the “floating” aspect of navigation banner 5160 isillustrated, as navigation banner 5160 continues to be displayedoverlying cover sheet user interface 504 (referred to above as wakescreen user interface 504) as cover sheet user interface 504 slides downto cover maps application user interface 5154. FIGS. 5DD-5DE illustratehow navigation banner 5160 is anchored to time/date object 582 in coversheet user interface 504.

FIGS. 5DB-5DF illustrate an input (e.g., a downward swipe) by a contacton touch screen 112 that is initiated at an upper edge of touch screen112, as indicated by focus selector 5162. In response to the input,cover sheet user interface 504 slides down from the upper edge ofdisplay 112, as shown in FIGS. 5DC-5DF. As shown in FIGS. 5DC-5DD,notifications 5164 and 5168 that are displayed on cover sheet userinterface 504 descend as cover sheet user interface 504 slides down,while navigation banner 5160 remains at a fixed position on cover sheet504 (e.g., cover sheet 504 and its notifications 5164 and 5168 appear toslide down behind navigation banner 5160). As shown in FIGS. 5DD-5DE, inaccordance with a determination that cover sheet user interface 504 hasdescended a threshold distance relative to navigation banner 5160,navigation banner 5160 becomes “attached” to the cover sheet userinterface and begins to move downward while cover sheet user interface504 moves downward. As shown in FIGS. 5DD-5DF, a time/date object 582that is displayed on cover sheet user interface 504 is graduallyrevealed as cover sheet user interface 504 moves downward. In accordancewith a determination that the time/date object 582 has reached apredefined location on the display, time/date object 582 and navigationbanner 5160 cease to move as the cover sheet user interface 504continues its descent (and notifications 5164 and 5168 continue to movedownward with the cover sheet user interface 504).

In FIG. 5DG, the contact indicated by focus selector 5162 has lifted offof cover sheet user interface 504.

FIGS. 5DH-5DI illustrate input at navigation banner 5160 to display theuser interface 5154 of the corresponding maps application.

In FIG. 5DH, an input (e.g., a tap input) by a contact on touch screen112 is detected at a location that corresponds to navigation banner5160, as indicated by focus selector 5168. In response to the input,cover sheet user interface 504 ceases to be displayed and mapsapplication user interface 5154 is redisplayed, as indicated at FIG.5DI. In FIG. 5DI, navigation banner 5160 is displayed on the navigationmode user interface of the maps application user interface 5154.

FIGS. 5DJ-5DS illustrate input to display a home screen user interface522 (over which navigation banner 5160 continues to be displayed), topull down cover sheet user interface 504 over home screen user interface522, and to show the continuous display of navigation banner 5160 ashome screen user interface 522 is revealed from under cover sheet 522.

FIG. 5DJ illustrates an input by a contact on touch screen 112 that isinitiated by a contact at location that corresponds to home affordance552, as indicated by focus selector 5170. In response to the input,display of map application user interface 5154 is replaced by display ofhome screen user interface 522, as shown in FIGS. 5DJ-5DM. Navigationbanner 5160 remains displayed at the same position during the transitionfrom displaying map application user interface 5154 to displaying homescreen user interface 522. Navigation banner 5160 is displayedoverlaying home screen user interface 522.

FIGS. 5DN-5DO illustrate an input (e.g., a downward swipe) that isinitiated by a contact at a location near the upper edge of touch screen112, as indicated by focus selector 5172. In response to the input,cover sheet user interface 504 slides down from the upper edge ofdisplay 112, as shown in FIGS. 5DN-5DP.

FIG. 5DQ illustrates an input (e.g., an upward swipe input) by a contacton touch screen 112 that is initiated by a contact at location indicatedby focus selector 5174. In response to the input, display of cover sheetuser interface 504 is replaced by display of home screen user interface522, as shown in FIGS. 5DQ-5DS.

FIG. 5DT-5DW illustrate input that causes transition of navigationbanner 5160 from a banner form (as shown in FIG. 5DT) to pill form (asshown in FIG. 5DW).

FIGS. 5DT-5DU illustrate an input (e.g., an upward swipe) that isinitiated by a contact at a location that corresponds to navigationbanner 5160, as indicated by focus selector 5176. In response to theinput, navigation banner 5160 gradually transitions from a bannerformat, as shown in FIG. 5DT, to a pill format, as shown in FIG. 5DW.For example, as navigation banner 5160 gradually transitions from abanner format to a pill format, an animation is displayed in whichnavigation text 5178 in navigation banner 5160 ceases to be displayed,navigation direction arrow 5180 shrinks, navigation banner 5160gradually shrinks and moves leftward, and a time 5182 is displayed(e.g., adjacent to navigation direction arrow 5180) in the pill formatof navigation banner 5160.

FIGS. 5DX-5DW illustrate input on navigation banner 5160 (in the pillformat) that causes an application that corresponds to the banner to bedisplayed.

In FIG. 5DX, an input (e.g., a tap input) by a contact on touch screen112 is detected at a location that corresponds to navigation banner 5160(in the pill format), as indicated by focus selector 5184. In responseto the input, because the content of navigation banner 5160 (in the pillformat) corresponds to the navigation mode of the map application, homescreen user interface 522 ceases to be displayed and maps applicationuser interface 5154 is redisplayed, as indicated at FIG. 5DY. In FIG.5DY, navigation banner 5160 is displayed on the navigation mode userinterface of the maps application user interface 5154.

FIGS. 5DZ-5EA illustrate banners that are displayed on device 100 whendevice 100 is in a screen-off state.

In FIG. 5DZ, device 100 has transitioned from the screen-on state, asshown in FIG. 5DY, to a screen-off state. Because the navigation mode ofthe map application was active when the device 100 transitioned to thescreen-off state, navigation banner 5160 is displayed on device 100while the device is in the “screen-off” state (e.g., aside fromdisplaying the navigation banner 5160, the display 112 is blank).

In FIG. 5EA, while the device 100 is in the “screen-off” state, anotification 5186 is received. The received notification 5186 isdisplayed on display 112 of device 100 while the device 100 is in the“screen-off state” (e.g., aside from displaying the receivednotification 5186 and/or the navigation banner 5160, the display 112 isblank).

In FIG. 5EB, device 100 has transitioned from the screen-off state, asshown in FIGS. 5DZ-5EA, to a screen-on state, and cover sheet userinterface 504 is displayed on the display 112 of device 100.

FIGS. 5EC-5GU illustrate example user interfaces for navigation using acover sheet in accordance with some embodiments. The user interfaces inthese figures are used to illustrate the processes described below,including the processes in FIGS. 9A-9C. For convenience of explanation,some of the embodiments will be discussed with reference to operationsperformed on a device with a touch-sensitive display system 112. In suchembodiments, the focus selector is, optionally: a respective finger orstylus contact, a representative point corresponding to a finger orstylus contact (e.g., a centroid of a respective contact or a pointassociated with a respective contact), or a centroid of two or morecontacts detected on the touch-sensitive display system 112. However,analogous operations are, optionally, performed on a device with adisplay 450 and a separate touch-sensitive surface 451 in response todetecting the contacts on the touch-sensitive surface 451 whiledisplaying the user interfaces shown in the figures on the display 450,along with a focus selector.

FIGS. 5EC1 to 5EC4 illustrate activation of a display (e.g.,touch-sensitive display 112) in response to changing an orientation ofdevice 100. When the display has been activated, notifications that werereceived while the device was in a screen-off state were received. Thesenotifications are displayed when the device transitions to a screen-onstate. In FIG. 5EC1, the device is in a screen-off state while it isheld flat in a user's hand 502, such that the device display issubstantially horizontal. In FIG. 5EC2, the device is tilted such thatthe display is more vertical than in FIG. 5EC1. Because a tilt angle ofthe device has not increased above a threshold tilt angle in FIG. 5EC2,the display is not activated. In FIG. 5EC3, the device is tilted suchthat the display is more vertical than in FIG. 5EC2. Because a tiltangle of the device has increased above a threshold tilt angle in FIG.5EC3, the display has transitioned from a screen-off state to ascreen-on state and wake screen user interface 504 (also referred toherein as a cover sheet user interface 504) is displayed by the display112. In FIG. 5EC4, the display 112 is substantially vertical.

FIG. 5ED illustrates a wake screen user interface 504, in accordancewith some embodiments. Wake screen user interface 504 displays missednotification 5188 that was received and/or generated by device 100(e.g., while device 100 was in a screen-off state). In some embodiments,wake screen user interface 504 additionally displays controls, such as asubset of controls from a control center user interface 5138 (e.g., aflashlight control 5190 and a camera control 5192).

In some embodiments, different input criteria must be met to activate aflashlight control 5190 when it is displayed on a wake screen userinterface 504 and when it is displayed in a control center userinterface 5138, as illustrated in FIGS. 5EE-5EJ and 5ET-5EW. Becausewake screen user interface 504 may be displayed (e.g., in response totilting the device) at a time when the user does not wish to provideinput, more stringent criteria are applied for operating controlsdisplayed on the wake screen user interface to prevent unintentionaloperation of the controls.

In some embodiments, input that has one effect when it is applied to acontrol (e.g., camera control 5192) when it is displayed in controlcenter user interface 5138 has a different effect when the control isdisplayed in wake screen user interface 504. For example, a light pressinput on camera control 5192 causes a menu 5220 to be displayed whencamera control 5192 is displayed in control center user interface 5138,and the light press input on camera control 5192 causes activation of acamera application when camera control 5192 is displayed in wake screenuser interface 504, as illustrated by FIGS. 5EX-5FN.

In some embodiments, a time/date object 582 shifts horizontally as inputfor navigating from wake screen user interface 504 to adjacent userinterfaces (control center user interface 5138 and widget user interface5140) to indicate the direction of input needed to return to the wakescreen user interface 504, as illustrate at FIGS. 5EJ-5EP and FIGS.5EQ-5ES and 5FF-5FH. An overview of the arrangement wake screen userinterface 504 to adjacent user interfaces control center user interface5138 and widget user interface 5140 is shown in FIG. 5FR.

FIGS. 5EE-5EG illustrate a first flashlight activation input (e.g., alight press input) by a contact with touch screen 112, as indicated byfocus selector 5194, at a location that corresponds to a flashlightcontrol 5190 that is displayed on wake screen user interface 504. InFIG. 5EE, a characteristic intensity of the contact is above a detectionthreshold IT₀, as indicated by intensity level meter 5196, and below alight press intensity level IT_(L). In FIG. 5EF, in accordance with adetermination that a characteristic intensity of the contact hasincreased above a light press intensity threshold, as indicated byIT_(L) on intensity level meter 5196, a flashlight is activated, asindicated by flashlight beam 5198. In FIG. 5EG, the contact indicated byfocus selector 5194 has lifted off of touch screen 112.

FIGS. 5EH-5EI illustrate a first flashlight deactivation input (e.g., alight press input) by a contact with touch screen 112 at a location thatcorresponds to flashlight control 5190, as indicated by focus selector5200. In FIG. 5EI, in accordance with a determination that acharacteristic intensity of the contact has increased above a lightpress intensity threshold, as indicated by IT_(L) on intensity levelmeter 5196 while the flashlight is on, the flashlight is shut off. InFIG. 5EJ, the contact indicated by focus selector 5200 has lifted off oftouch screen 112.

FIGS. 5EK-5EL illustrate an input (e.g., a rightward swipe) that isinitiated by a contact on touch screen 112, as indicated by focusselector 5202. In response to the input, wake screen user interface 504slides to the right and mini application user interface 5140 isrevealed, as shown in FIGS. 5EK-5EM. Mini application user interface5140 displays mini application objects 583, 585, 587, and 589 thatinclude a subset of content from application. As wake screen userinterface 504 slides to the right, time/date object 582 moves from aposition in the center of the display 112, as shown in FIG. 5EK, to aposition at the right of the display 112, as shown in FIG. 5EM.Repositioning time/date object 582 provides a visual indication to theuser of the direction of the swipe input needed to return to wake screen504.

In some embodiments, a mini application object (e.g., as illustrated bymini application objects 583, 585, 587, and 589) is configured toperform a subset, less than all, of the functions of a correspondingapplication. In some embodiments, a mini application object displays anidentifier for the corresponding application. In some embodiments, amini application object displays a portion of the content thecorresponding application. In some embodiments, a predefined input on amini application object launches the corresponding application. In someembodiments, a mini application object operates as a standaloneapplication residing in memory of the device, distinct from anassociated application also residing in the memory of the device. Forexample, a mini application object corresponding to a social networkingapplication operates as a single-purpose or streamlined application witha subset, less than all, of the functionality of the correspondingapplication, but is associated with the full-featured social networkingapplication. In this example, the mini application object operatesindependently of the social networking application, and in a scenariowhere the social networking application is not running, the miniapplication object continues to operate. In some embodiments, a miniapplication object operates as an extension or component of anassociated application on the device.

FIGS. 5EN-5EO illustrate an input (e.g., a leftward swipe) that isinitiated by a contact on touch screen 112, as indicated by focusselector 5204. In response to the input, mini application user interface5140 slides to the left and wake screen user interface 504 is revealed,as shown in FIG. 5EN-5EP. As mini application user interface 5140 slidesto the left, time/date object 582 moves from a position in at the rightof the display 112, as shown in FIG. 5EN, to a position in the center ofthe display 112, as shown in FIG. 5EP. Repositioning time/date object582 provides a visual indication to the user of the direction of theswipe input needed to return to wake screen 504.

FIGS. 5EQ-5ER illustrate an input (e.g., a leftward swipe) that isinitiated by a contact on touch screen 112, as indicated by focusselector 5206. In response to the input, wake screen user interface 504slides to the left and control center user interface 5138 is revealed,as shown in FIG. 5EQ-5ES. As wake screen user interface 5140 slides tothe left, time/date object 582 moves from a position in at the center ofthe display, as shown in FIG. 5EQ, to a position at the left of thedisplay, as shown in FIG. 5ES. Repositioning time/date object 582provides a visual indication to the user of the direction of the swipeinput needed to return to wake screen 504.

FIG. 5ET illustrates a second flashlight activation input (e.g., a tapinput) by a contact with touch screen 112, as indicated by focusselector 5208, at a location that corresponds to a flashlight control5190 that is displayed on control center user interface 5138. Inresponse to the input, a flashlight is activated, as indicated byflashlight beam 5210 in Figure EU. Because a wake screen user interface504 is displayed on waking the device (e.g., when the device is tiltedas described with regard to FIGS. 5EC1-5EC4), input that meets thresholdintensity criteria (e.g., light press intensity criteria) is needed toactivate the flashlight using a flashlight control 5190 displayed in thewake screen user interface 504. In this way, accidental activation ofthe flashlight is avoided. When the user has provided input to navigateto control center user interface 5138, a tap input (as described withregard to FIGS. 5ET-5EU) is sufficient to activate the flashlight.

FIG. 5EV illustrates a second flashlight deactivation input (e.g., a tapinput) by a contact with touch screen 112 at a location that correspondsto flashlight control 5190, as indicated by focus selector 5212. Inresponse to the input, the flashlight is shut off, as indicated at FIG.5EW.

FIG. 5EX illustrates a control center camera application activationinput (e.g., a tap input) by a contact with touch screen 112, asindicated by focus selector 5214, at a location that corresponds to acamera control 5192 that is displayed on control center user interface5138. In response to the control center camera application activationinput, display of the control center user interface 5138 is replaced bydisplay of a camera application user interface 5216, as shown in FIG.5EY.

FIGS. 5EZ-5FB illustrate camera menu display input (e.g., a light pressinput) by a contact with touch screen 112, as indicated by focusselector 5218, at a location that corresponds to a camera control 5192that is displayed on control center user interface 5138. In FIG. 5FA, acharacteristic intensity of the contact is above a detection thresholdIT₀, as indicated by intensity level meter 5196, and below a light pressintensity level IT_(L). In FIG. 5FB, in accordance with a determinationthat a characteristic intensity of the contact increases above a lightpress intensity threshold, as indicated by IT_(L) on intensity levelmeter 5196, a camera menu 5220 is displayed overlaying control centeruser interface 5138.

In FIG. 5FC, the contact indicated by focus selector 5218 has lifted offfrom touch screen 112.

In FIG. 5FD, an input (e.g., a tap input) by a contact on touch screen112 is detected at a location outside of camera menu 5220, as indicatedby focus selector 5222. In response to the input, camera menu 5220ceases to be displayed overlaying control center user interface 5138, asshown in FIG. 5FE.

FIGS. 5FF-5FG illustrate an input (e.g., a rightward swipe) that isinitiated by a contact on touch screen 112, as indicated by focusselector 5224. In response to the input, control center user interface5138 slides to the right and wake screen user interface 504 isredisplayed, as shown in FIGS. 5FG-5FH. As control center user interface5138 slides to the right, time/date object 582 moves from a position inthe left of the display, as shown in FIG. 5FF, to a position at thecenter of the display, as shown in FIG. 5FH.

FIG. 5FI illustrates an input (e.g., a tap input) by a contact withtouch screen 112, as indicated by focus selector 5226, at a locationthat corresponds to a camera control 5192 that is displayed on wakescreen user interface 504. As shown in FIGS. 5FI-5FJ, a tap input oncamera control 5192 that is displayed on wake screen user interface 504has no effect (unlike a tap input on camera control 5192 displayed incontrol center user interface 5138, which causes a camera applicationuser interface 5216 to be displayed, as discussed with regard to FIGS.5EX-5EY).

Whereas a light press input on a camera control displayed in controlcenter user interface 5138 causes a camera menu 5220 to be displayed, alight press input on a camera control displayed in wake screen userinterface 504 causes a camera application user interface 5216 to bedisplayed. FIGS. 5FK-5FL illustrate a wake screen camera activationinput (e.g., a light press input) by a contact with touch screen 112, asindicated by focus selector 5228, at a location that corresponds to acamera control 5192 that is displayed on wake screen user interface 504.In FIGS. 5FK-5FL, a characteristic intensity of the contact is above adetection threshold IT₀, as indicated by intensity level meter 5196, andbelow a light press intensity level IT_(L). In FIG. 5FM, in accordancewith a determination that a characteristic intensity of the contact hasincreased above a light press intensity threshold, as indicated byIT_(L) on intensity level meter 5196, display of the wake screen userinterface 504 is replaced by display of a camera application userinterface 5216.

FIGS. 5FN-5FT illustrate that, in response to authentication input(e.g., as shown in FIG. 5FP, additional notification information isdisplayed on wake screen user interface 504.

FIG. 5FN illustrates an input (e.g., an upward swipe) by a contact ontouch screen 112 that is initiated at a lower edge of touch screen 112,as indicated by focus selector 5230. In response to the input, inaccordance with a determination that the device is locked, anauthentication user interface 518 is displayed, as shown in FIG. 5FO.

In FIG. 5P, an authentication input (e.g., a tap input) by a contact ontouch screen 112 is detected at a location within authentication userinterface 518, as indicated by focus selector 5232. In response to theauthentication input, the device is unlocked and home screen userinterface 522 is displayed, as shown in FIG. 5FQ.

FIG. 5FR illustrates an input (e.g., a downward swipe) that is initiatedby a contact at a location near the upper edge of touch screen 112, asindicated by focus selector 5232. In response to the input, wake screenuser interface 504 slides down from the upper edge of display 112, asshown in FIGS. 5FR-5FT. When wake screen user interface 504 is displayedwhile device 100 is unlocked, as shown in FIG. 5FT, notification 5188 isdisplayed with information (e.g., message text 5234 and an image 5236)that were not displayed while device 100 was locked (see, e.g., FIG.5ED), and an additional notification 5190 is displayed.

FIG. 5FU illustrates an arrangement of wake screen user interface 504and adjacent user interfaces control center user interface 5138 andwidget user interface 5140. As discussed above with regard to FIGS.5EK-5EP, a rightward swipe on wake screen user interface 504 causeswidget user interface 5140 to be displayed, and a leftward swipe onwidget user interface 5140 causes wake screen user interface 504 to bedisplayed. As discussed above with regard to FIGS. 5EQ-5ES and FIGS.5FF-5FH, a leftward swipe on wake screen user interface 504 causescontrol center user interface 5138 to be displayed, and a rightwardswipe on control center user interface 5138 causes wake screen userinterface 504 to be displayed. An upward swipe on wake screen userinterface 504 causes a previously displayed user interface (e.g., homescreen user interface 522, an application user interface, or a settingsuser interface) to be displayed.

As illustrated in FIGS. 5FV-5GB, when input to display widget userinterface 5140 or control center user interface 5138 is received, thestate of a user interface that is adjacent to wake screen user interface504 being displayed is not “sticky,” in that when widget user interface5140 or control center user interface 513 are displayed and subsequentlydismissed, a subsequent downward swipe input from the upper edge ofdisplay 112 will cause wake screen user interface 504 (and not widgetuser interface 5140 or control center user interface 513) to bedisplayed.

FIGS. 5FV-5FW illustrate an input (e.g., a rightward swipe) that isinitiated by a contact on touch screen 112, as indicated by focusselector 5238. In response to the input, wake screen user interface 504slides to the right and mini application user interface 5140 isrevealed, as shown in FIGS. 5FV-5FX.

FIG. 5FY illustrates an input (e.g., an upward swipe) by a contact ontouch screen 112 that is initiated at a lower edge of touchscreen 112 bya contact at location that is indicated by focus selector 5240. Inresponse to the input, display of mini application user interface 5140is replaced by display of home screen user interface 522, as shown inFIGS. 5FY-5FZ.

In FIGS. 5FZ-5GB, after an input is received for navigation to a userinterface that is adjacent to wake screen user interface 504 (e.g., tonavigate to mini application user interface 5140 or control center userinterface 5138) and a subsequent input is received to dismiss the userinterface that is adjacent to wake screen user interface 504 (e.g., theinput in FIG. 5FY to reveal home screen 522), a downward swipe revealswake screen user interface 504 (and not the adjacent interface that wasdisplayed prior to the dismissal input). For example, in FIG. 5FZ, aninput (e.g., a downward swipe) is initiated by a contact at a locationnear the upper edge of touch screen 112, as indicated by focus selector5242. In response to the input, wake screen user interface 504 (and notmini application user interface 5140) slides down from the upper edge ofdisplay 112, as shown in FIGS. 5FZ-5GB.

FIGS. 5GC-5GP illustrate input to display a maps application, activate anavigation mode of the maps application and display a navigation banner5160, and transition the navigation banner 5160 from a pill form, asshown in FIG. 5FM, to a banner form, as shown in FIG. 5GP, in accordancewith some embodiments.

FIG. 5GC illustrates an input (e.g., an upward swipe) by a contact ontouch screen 112 that is initiated by a contact at location thatcorresponds to home affordance 552, as indicated by focus selector 5244.In response to the input, display of wake screen user interface 504 isreplaced by display of home screen user interface 522, as shown in FIGS.5GC-5GD.

In FIG. 5GE, an input (e.g., a tap input) is detected at a location thatcorresponds to affordance 5248 for displaying a maps applicationinterface, as indicated by focus selector 5246. In response to theinput, a maps application user interface 5154 is displayed, as shown inFIG. 5GF.

In FIG. 5GH, an input (e.g., a tap input) by a contact on touch screen112 is detected at a location that corresponds to a control 5156 foractivating a navigation mode of the maps application, as indicated byfocus selector 5250. In response to the input, the navigation mode ofthe maps application is initiated, and a navigation mode user interfaceis displayed in maps application user interface 5154, as indicated atFIG. 5GI.

FIG. 5GJ illustrates an input (e.g., an upward swipe) by a contact ontouch screen 112 that is initiated by a contact at location thatcorresponds to home affordance 552, as indicated by focus selector 5252.In response to the input, display of wake screen user interface 504 isreplaced by display of home screen user interface 522, as shown in FIGS.5GK-5GL. In FIG. 5GL, a navigation banner 5160 is displayed in a pillformat within home screen user interface 522.

FIGS. 5GM-5GO illustrate an input (e.g., a downward swipe) that isinitiated by a contact at a location near the upper edge of touch screen112, as indicated by focus selector 5254. In response to the input, wakescreen user interface 504 slides down from the upper edge of display112, as shown in FIGS. 5GM-5GP. As wake screen user interface 504 slidesdown, navigation banner 5160 transitions from a pill format, as shown inFIG. 5GM, to a banner format, as shown in FIG. 5GP. For example, asnavigation banner 5160 gradually transitions from a pill format to abanner format, an animation is displayed in which navigation text 5178is displayed in navigation banner 5160, navigation direction arrow 5180grows, navigation banner 5160 gradually grows and moves toward thecenter of display 112, and time 5182 ceases to be displayed.

From FIG. 5GP to FIG. 5GQ, the information displayed in navigationbanner 5160 has updated (e.g., in accordance with a changed location ofthe phone as the user proceeds along the navigation route), indicatingthat the content of navigation banner 5160 updates (e.g., in real time)while navigation banner 5160 is displayed.

FIG. 5GR illustrates an input (e.g., an upward swipe) by a contact ontouch screen 112 that is initiated at a location near the lower edge oftouch screen 112, as indicated by focus selector 5256. In response tothe input, wake screen user interface 504 slides up from the lower edgeof display 112 to redisplay the underlying maps user interface 5154(that was previously covered by wake screen user interface 504).

FIG. 5GT illustrates an input (e.g., an upward swipe) by a contact ontouch screen 112 that is initiated by a contact at location thatcorresponds to home affordance 552, as indicated by focus selector 5258.In response to the input, display of wake screen user interface 504 isreplaced by display of home screen user interface 522, as shown in FIGS.5GT-5GU. In FIG. 5GU, because the navigation mode of maps application5154 is still active, a navigation banner 5160 is displayed in a pillformat within home screen user interface 522.

From FIG. 5GL to FIG. 5GU, the information displayed in the pill formatversion of navigation banner 5160 has updated (e.g., in accordance witha changed location of the phone as the user proceeds along thenavigation route), indicating that the content of the pill formatversion of navigation banner 5160 updates (e.g., in real time) whilenavigation banner 5160 is displayed.

In FIGS. 5GV-5GW, the color of one or more objects on wake screen userinterface 504 (e.g., time/date object 582, navigation banner 5188,notification 5188, and/or notification 5234) are altered in accordancewith a change in a background color and/or image of wake screen userinterface 504.

FIGS. 5GX-5HR illustrate a panel-based cover sheet user interface 5260(e.g., a wake screen displayed on a device with a large format display,such as a tablet device). In some embodiments, when panel-based coversheet user interface 5260 is dismissed and subsequently recalled, astate of the panel-based cover sheet user interface 5260 whenpanel-based cover sheet user interface 5260 is recalled is the same asthe state of panel-based cover sheet user interface 5260 prior to thedismissal.

In FIG. 5GX, panel-based cover sheet user interface 5260 is displayed ondisplay 112. A notification panel 5262 is displayed on panel-based coversheet user interface 5260.

FIGS. 5GY-5GZ illustrate an input (e.g., a rightward swipe) that isinitiated by a contact on touch screen 112, as indicated by focusselector 5264. In response to the input, notification panel 5262 slidesto the right and a mini application panel 5266 is revealed, as shown inFIGS. 5GZ-5HA. In FIG. 5HA, notification panel 5262 and mini applicationpanel 5266 are simultaneously displayed on panel-based cover sheet userinterface 5260.

FIGS. 5HB-5HC illustrate an input (e.g., an upward swipe) by a contacton touch screen 112 that is initiated at a lower edge of touchscreen 112by a contact at location that is indicated by focus selector 5268. Inresponse to the input, panel-based cover sheet user interface 5260slides upward to reveal home screen user interface 522, as shown inFIGS. 5HB-5HD.

FIGS. 5RE-5HF illustrate an input (e.g., a downward swipe) by a contacton touch screen 112 that is initiated at an upper edge of touchscreen112 by a contact at location that is indicated by focus selector 5272.In response to the input, panel-based cover sheet user interface 5272slides downward over home screen user interface 522, as shown in FIGS.5RE-5HG. Notification panel 5262 and mini application panel 5266, whichwere simultaneously displayed on panel-based cover sheet user interface5260 prior to dismissal of panel-based cover sheet user interface 5272,continue to be displayed when panel-based cover sheet user interface5260 is redisplayed.

FIGS. 5HH-5HI illustrate an input (e.g., a leftward swipe) that isinitiated by a contact on touch screen 112, as indicated by focusselector 5274. In response to the input, notification panel 5274 slidesto the left, until notification panel 5274 ceases to be displayed, and acontrol center panel 5278 is revealed, as shown in FIGS. 5HH-5HL. InFIG. 5HL, notification panel 5262 and control center panel 5278 aresimultaneously displayed on panel-based cover sheet user interface 5260.

FIGS. 5HM-5HN illustrate an input (e.g., an upward swipe) by a contacton touch screen 112 that is initiated at a lower edge of touchscreen 112by a contact at location that is indicated by focus selector 5278. Inresponse to the input, panel-based cover sheet user interface 5260slides upward to reveal home screen user interface 522, as shown inFIGS. 5HM-5HO.

FIGS. 5HP-5HF illustrate an input (e.g., a downward swipe) by a contacton touch screen 112 that is initiated at an upper edge of touchscreen112 by a contact at location that is indicated by focus selector 5280.In response to the input, panel-based cover sheet user interface 5272slides downward over home screen user interface 522, as shown in FIGS.5HP-5HR. Notification panel 5262 and control center panel 5278, whichwere simultaneously displayed on panel-based cover sheet user interface5260 prior to dismissal of panel-based cover sheet user interface 5272,continue to be displayed when panel-based cover sheet user interface5260 is redisplayed.

FIGS. 6A-6G are flow diagrams illustrating method 600 of clearing setsof notifications, in accordance with some embodiments. Method 600 isperformed at an electronic device (e.g., device 300, FIG. 3, or portablemultifunction device 100, FIG. 1A) with a display, a touch-sensitivesurface, and one or more sensors to detect intensity of contacts withthe touch-sensitive surface. In some embodiments, the display is atouch-screen display and the touch-sensitive surface is on or integratedwith the display. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 600 are, optionally,combined and/or the order of some operations is, optionally, changed.

As described below, method 600 provides an intuitive way to clear setsof notifications. The method reduces the number, extent, and/or natureof the inputs from a user when clearing sets of notifications, therebycreating a more efficient human-machine interface. For battery-operatedelectronic devices, enabling a user to clear sets of notificationsfaster and more efficiently conserves power and increases the timebetween battery charges.

While the device is in a screen-off state (e.g., as shown in FIGS.5A1-5A2), the device receives (602) one or more notifications.

After receiving the one or more notifications (e.g., while the deviceremains in the screen-off state, or while the one or more notificationsare displayed on a dark screen of the screen-off state), the devicedetects (604) a first input from a user for waking the device from thescreen-off state to a screen-on state (e.g., the device detects a statechange indicating that the device has been picked up, as described withregard to FIGS. 5A1-5A4, or the device detects an input at a control,such as push button 106, for waking the device).

In response to detecting the first input for waking the device from thescreen-off state to the screen-on state, the device (606): transitionsthe device from the screen-off state to the screen-on state (e.g., asshown at FIGS. 5A2-5A3), displays a wake screen user interface 504 onthe display 112 (as shown in FIGS. 5A3 and 5B), and displays the one ormore notifications (e.g., notifications 506, 508, 510, and 512 shown inFIG. 5B) on the wake screen user interface 504 (e.g., the notificationsare displayed as a list of notification banners below a time-date object582). These notifications are sometimes also referred to as “missednotifications” because they were received while the device was in thescreen-off state. In some embodiments, the wake screen user interface504 is also a cover sheet user interface that is displayed to cover acurrently displayed user interface when a downward edge swipe gesture(e.g., a downward swipe that starts from an upper edge of thetouch-sensitive surface 112) is detected on the display 112. In someembodiments, the wake screen user interface 504 includes a time-dateobject 582 showing the current time and date, and/or one or more promptsor affordances for unlocking the device from a locked state to anunlocked state.

While displaying the wake screen user interface 504 and while at leastone of the one or more notifications remains displayed on the wakescreen user interface 504 (e.g., at a later time after the user hasinteracted with the device which may include interactions that cause thedismissal and then redisplay of the wake screen user interface one ormore times), the device detects (608) a second input for dismissing thewake screen user interface (e.g., an upward swipe input to reveal anunderlying user interface or an input (e.g., on a power button) to shutoff the display).

In response to detecting the second input for dismissing the wake screenuser interface, the device ceases (610) to display the wake screen userinterface 504 and the at least one of the one or more notifications(e.g., notifications 506, 508, 510, and 512 shown in FIG. 5B). In someembodiments, the device reveals an underlying interface such as a homescreen user interface 522, a settings user interface, or an applicationuser interface (e.g., messages user interface 530, web browser userinterface 540, music user interface 560, or maps user interface 5154.

After ceasing to display the wake screen user interface 504 and the atleast one of the one or more notifications in response to the secondinput, the device detects (612) a third input for redisplaying the wakescreen user interface (e.g., the third input may be an input for wakingthe device again after the device has transitioned back to thescreen-off state, or an input (e.g., a downward swipe from the top ofthe touch-screen) for redisplaying the wake screen user interface afterthe wake screen user interface has been dismissed while the deviceremains in the screen-on state).

In response to detecting the third input for redisplaying the wakescreen user interface 504 (614), in accordance with a determination thatthe third input meets notification-clearance criteria (e.g.,notification-clearance criteria are criteria for completely removing allremaining missed notifications from the wake screen user interface and,optionally, deleting the notifications or saving them to notificationhistory), the device redisplays the wake screen user interface 504without displaying the at least one of the one or more notifications onthe redisplayed wake screen user interface 504 (e.g., all previouslydisplayed missed notifications are cleared from the wake screen userinterface). The notification-clearance criteria require that the thirdinput is detected at a time that is (1) after a respective notificationof the one or more notifications has been cleared through direct userinteraction with the respective notification or an application thatcorresponds to the respective notification and (2) after the device hastransitioned from the screen-on state to the screen-off state at leastonce since the detection of the second input (e.g., since the last inputfor dismissing the wake screen user interface was detected). Examples ofuser interaction with the respective notification include an input toactivate a displayed deletion control, such as an “x” icon displayedadjacent to the notification (e.g., a tap gesture by a contact at alocation that corresponds to the displayed control), an input (such as adeep press or swipe gesture) on the notification to dismiss or deletethe notification or to reveal a control for dismissing the notificationfollowed by an input to activate a control for dismissing thenotification, or an input to open the notification in an application(e.g., a tap gesture by a contact at a location that corresponds to thenotification). For example, the input described with regard to FIGS.5AV-5AW (e.g., the input to wake the device) is detected at a time thatis detected at a time that is (1) after a respective notification of theone or more notifications has been cleared through direct userinteraction with the respective notification or an application thatcorresponds to the respective notification (e.g., described with regardto FIGS. 5L-5P and FIGS. 5Y-5AC) and (2) after the device hastransitioned from the screen-on state to the screen-off state at leastonce since the detection of the second input (e.g., as described withregard to FIGS. 5AU-5AW). In accordance with a determination that thethird input does not meet the notification-clearance criteria: thedevice redisplays the wake screen user interface, and redisplays the atleast one of the one or more notifications on the redisplayed wakescreen user interface (e.g., continuing to display all of thenotifications that were not dismissed by the user through direct userinteraction (e.g., all or a subset of all the missed notifications thatwere received during the screen-off state)).

This heuristic allows a device to either automatically clear a set ofmissed notifications or to redisplay a set of missed notificationsdisplayed on a wake screen depending on whether notification-clearancecriteria are met. Automatically clearing a set of missed notificationsin accordance with a determination that notification-clearance criteriaare met makes the user-device interface more efficient and enhances theoperability of the device by providing the user with the ability toclear multiple notifications without requiring the user to manuallydismiss each notification, while retaining the ability of the user toindividually clear missed notifications in the set of multiplenotifications (e.g., by maintaining the device in a screen-on sessionwhile interacting with the individual notifications). Enabling the userto use the device more quickly and efficiently reduces power usage andimproves battery life of the device.

In some embodiments, in response to detecting the third input forredisplaying the wake screen user interface, and in accordance with thedetermination that the third input does not meet thenotification-clearance criteria (616), in accordance with adetermination that one or more notification-clearance interactions haveoccurred (e.g., through a direct user interaction with a notification orinteraction with an application that corresponds to a notification), thedevice forgoes display of one or more notifications that are cleared bythe one or more notification-clearance interactions on the redisplayedwake screen user interface 504. For example, notification-clearanceinteractions are described with regard to described with regard to FIGS.5L-5P and FIGS. 5Y-5AC. In FIG. 5P, notification 510 is not displayeddue to interaction with notification 510 that occurred in FIG. 5L (tocause display of messages application 530). In FIG. 5AC, notification506 is not displayed due to the interaction with notification 506 thatoccurred in Figure AB (to cause deletion of the notification). In someembodiments, in accordance with a determination that nonotification-clearance interactions have occurred, all of the one ormore notifications are redisplayed on the redisplayed wake screen userinterface.

Forgoing display of one or more notifications that are cleared by theone or more notification-clearance interactions on the redisplayed wakescreen user interface reduces the amount of information displayed on theredisplayed wake screen. Reducing the amount of information displayed onthe redisplayed wake screen makes the user-device interface moreefficient and enhances the operability of the device by allowing a userto access notification information that the user has not previouslyreviewed without having to navigate past information that the user haspreviously reviewed.

In some embodiments, after detecting the first input for waking thedevice from the screen-off state to the screen-on state and prior todetecting the second input for dismissing the wake screen user interface(618), the device detects a plurality of intermediate inputs, theplurality of intermediate inputs including: a first intermediate inputfor dismissing the wake screen user interface (in response to which thewake screen is dismissed and a background user interface is revealed, orin response to which the device goes into the screen-off state and thescreen is dark with no interface displayed), and a second intermediateinput for redisplaying the wake screen user interface (in response towhich the wake screen is redisplayed over a currently displayed userinterface, or in response to which the device is woken to the screen-onstate and the wake-screen user interface is displayed as soon as thedisplay is turned on). For example, in FIGS. 5B-5C, the devicetransitions from a screen-on state to a screen-off state (e.g., inresponse to a user input to shut off the display), and at FIGS. 5C-5D,the device transitions back to a screen-on state (e.g., in response to auser input to wake the display). In FIGS. 5Q-5R, wake screen 504 isdismissed, and in FIGS. 5V-5X, wake screen 504 is redisplayed.

Maintaining display of a set of missed notifications after detectingintermediate inputs for dismissing and redisplaying a wake screen userinterface makes the user-device interface more efficient and enhancesthe operability of the device by allowing a user to display the wakescreen repeatedly (e.g., to view the time or check for an incomingnotification) while maintaining a list of missed notifications for theuser to handle when the user is ready to interact with the notifications(without requiring the user to provide input for redisplaying the missednotifications while the wake screen is displayed).

In some embodiments (620), the second input for dismissing the wakescreen user interface is an input for displaying a first user interface(e.g., an application user interface such as messages user interface 530or music user interface 560, a settings management user interface, aspringboard user interface (home screen user interface 522) thatincludes a plurality of application launch icons, etc.) that is distinctfrom the wake screen user interface, the first user interface isdisplayed in response to the second input (e.g., after the wake screenuser interface is dismissed, the first user interface is revealed fromunderneath the wake screen user interface), and the third input forredisplaying the wake screen user interface was received while the firstuser interface is displayed. For example, in FIGS. 5L-5M, an wake screenuser interface 504 is dismissed in response to user input that causesmessages user interface 530 to be displayed. While messages userinterface 530 is displayed, input to redisplay wake screen userinterface is received as described with regard to FIGS. 5N-5P.

Redisplaying the wake screen in response to input received while a firstuser interface (such as an application user interface, a springboarduser interface, or a settings management user interface) is displayedallows a user to access the wake screen (and any missed notificationsdisplayed on the wake screen) at all times while using the device. Thismakes the user-device interface more efficient and enhances theoperability of the device by allowing a user to access the wake screenwithout requiring the user to navigate through multiple interfaces togain access to the wake screen).

In some embodiments (622), the third input for redisplaying the wakescreen user interface 504 is received while a content playbackapplication is active (e.g., in response to an activation input asdescribed with regard to FIG. 5AK), and redisplaying the wake screenuser interface includes displaying (e.g., above the one or more missednotifications) at least one media playback control 572 (e.g., in a mediaplayback control panel 568) in the wake screen user interface 504. Insome embodiments, the playback controls are displayed on the wake screenuser interface 504 whenever the wake screen user interface is displayedwhile the content playback application is active (e.g., media playbackis ongoing).

Displaying at least one media playback control on the wake screen userinterface (e.g., in addition to the time and/or missed notifications)while a content playback application is active allows a user to controlplayback via the displayed media playback control immediately uponwaking the device, or by accessing the wake screen at any time whileusing the device. This makes the user-device interface more efficientand enhances the operability of the device by allowing a user to viewthe time and/or missed notifications while accessing the device tocontrol media playback without needing to unlock the device and/ornavigate through multiple interfaces.

In some embodiments, while the wake screen user interface 504 isdisplayed, the device detects (624) a fourth input by a contact on thetouch-sensitive surface, including detecting movement of the contactalong the touch-sensitive surface in a first direction (e.g., downwards)and detecting lift-off of the contact after the movement (e.g., asdescribed with regard to FIGS. 5AW-5AZ). In response to detecting thefourth input, the device: moves at least one object (e.g., an object 582that displays a current time and/or date) displayed on the wake screenuser interface 504 (e.g., in the first direction) in accordance with themovement of the contact, and reverses the movement of the at least oneobject (e.g., moving in a second direction opposite the first direction,e.g., upwards) upon lift-off of the contact.

Providing visual feedback, such as a “rubber band effect” simulated bymoving at least one object in accordance with movement of a contact andreversing the movement of the at least one object upon lift-off of thecontact, enhances operability of the device by providing an intuitiveindication to the user that the wake screen is responsive to input suchas a swipe input) to view additional notifications and thereby helpingthe user to provide proper inputs to achieve a desired outcome. Theindication is intuitive because the user receives the informationwithout the need to display additional instruction to the user forunderstanding the feature).

In some embodiments, while displaying the one or more notifications onthe wake screen user interface, the device detects (626) a fifth inputby a contact on the touch-sensitive surface (e.g., a tap input) at alocation that corresponds to a first notification of the one or morenotifications. In response to detecting the fifth input, the deviceceases to display the wake screen user interface and displays a firstapplication user interface for a first application that corresponds tothe first notification. For example, in FIG. 5L, an input at a locationthat corresponds to notification 510 is detected. In FIG. 5M, inresponse to the detected input, messages application user interface 530is displayed.

Displaying an application user interface for an application thatcorresponds to a notification in response to input detected at alocation that corresponds to the notification makes the user-deviceinterface more efficient and enhances the operability of the device byallowing a user to interact with an application with minimal inputimmediately upon waking the device or otherwise accessing a missednotification on the wake screen user interface.

In some embodiments, while displaying the first application userinterface for the first application that corresponds to the firstnotification (e.g., messages application user interface 530, as shown inFIGS. 5M-5N), the device detects (628) a sixth input for redisplayingthe wake screen user interface (e.g., an input as described with regardto FIGS. 5N-5O). In response to detecting the sixth input forredisplaying the wake screen user interface, the device ceases todisplay the first application user interface (e.g., as shown in FIG.5O), displays the wake screen user interface (e.g., as shown in FIG.5P), displays at least one second notification of the one or morenotifications on the wake screen user interface (e.g., notifications506, 508, and 512), wherein the at least one second notificationcorresponds to a second application that is distinct from the firstapplication, and forgoes display of the first notification (and,optionally, any other notifications among the one or more missednotifications that correspond to the first application) on the wakescreen user interface 504 with the at least one second notification. Forexample, in FIG. 5P, notification 510 is no longer displayed.

Forgoing display of a notification on the wake screen user interfaceafter displaying an application interface of an application thatcorresponds to the notification reduces the amount of informationdisplayed on the redisplayed wake screen. Reducing the amount ofinformation displayed on the redisplayed wake screen makes theuser-device interface more efficient and enhances the operability of thedevice by allowing a user to access notification information that theuser has not previously reviewed without having to navigate pastinformation that the user has previously reviewed (e.g., when accessingan application interface for an application that corresponds to thenotification).

In some embodiments, after detecting the sixth input, while displayingthe wake screen user interface 504, the device detects (630) a seventhinput for dismissing the wake screen user interface (e.g., includingdetecting an upward swipe gesture on the touch-sensitive surface). Inresponse to detecting the seventh input for dismissing the wake screenuser interface, the device ceases to display the wake screen userinterface (e.g., by pulling the wake screen user interface 504, which isused as a “cover sheet” user interface, upward), and redisplays thefirst application user interface for the first application. For example,FIGS. 5Q-5R show an input that causes wake screen user interface 504 toslide up to reveal the underlying messages application user interface530.

Redisplaying a last displayed user interface after dismissing the wakescreen user interface allows the user to return to a previous operatingcontext without requiring multiple inputs, thereby making theuser-device interface more efficient (e.g., by reducing the number ofinputs needed to return to a previously viewed user interface).

In some embodiments, while the first application user interface for thefirst application (e.g., messages user interface 530 for a messagesapplication) is redisplayed, the device detects (632) an eighth input(e.g., as described with regard to FIGS. 5S-5T) for invoking a thirdapplication that is distinct from the first application and the secondapplication. In response to detecting the eighth input for invoking thethird application, the device displays a third application userinterface of the third application (e.g., browser application userinterface 540 for a web browser application). After detecting the eighthinput, while displaying the third application user interface, the devicedetects a ninth input (e.g., as described with regard to FIG. 5V-5W) forredisplaying the wake screen user interface (e.g., including detecting adownward edge swipe gesture (e.g., a downward swipe that starts from anupper edge of the touch-sensitive surface 112)). In response todetecting the ninth input for redisplaying the wake screen userinterface 504, the device ceases to display the third application userinterface, displays the wake screen user interface 504 (e.g., pull downthe wake screen user interface over the second application userinterface), and redisplays the at least one second notification of theone or more notifications on the wake screen user interface withoutredisplaying the first notification (or, optionally, any missednotifications that correspond to the first application and the thirdapplication). For example, in FIG. 5X, wake screen 504 is displayed withnotifications 506, 508, and 512.

Maintaining display of a set of missed notifications after detectingintermediate inputs for dismissing and redisplaying a wake screen userinterface makes the user-device interface more efficient and enhancesthe operability of the device by allowing a user to display the wakescreen repeatedly (e.g., to view the time or check for an incomingnotification) while maintaining a list of missed notifications for theuser to handle when the user is ready to interact with the notifications(without requiring the user to provide input for redisplaying the missednotifications while the wake screen is displayed).

In some embodiments, after displaying the at least one secondnotification without displaying the first notification on the wakescreen user interface (e.g., in FIG. 5AU, notifications 508 and 512 aredisplayed and notifications 506 and 510 are no longer displayed), thedevice detects (634) a first transition from the screen-on state to thescreen-off state (e.g., the transition is triggered when an amount oftime that has passed since a last input was received increased above athreshold time, or when an input is received at a control for shuttingoff the display) followed by a second transition from the screen-offstate to the screen-on state (e.g., when an input is received to wakethe device or turn on the display). For example, FIGS. 5AU-5AVillustrate a transition from the screen-on state to the screen-off stateand FIGS. 5AV-5AW illustrate a transition from the screen-off-state tothe screen-on state. In response to detecting the first transitionfollowed by the second transition: the device redisplays the wake screenuser interface without displaying any of the one or more notificationson the wake screen user interface (e.g., the notification-clearancecriteria are met, and all of the missed notifications that were stillremaining on the wake screen are now cleared). For example, in FIG. 5AW,no notifications are displayed.

Automatically clearing a set of missed notifications in accordance witha determination that notification-clearance criteria are met makes theuser-device interface more efficient and enhances the operability of thedevice by providing the user with the ability to clear multiplenotifications without requiring the user to manually dismiss eachnotification. Enabling the user to use the device more quickly andefficiently reduces power usage and improves battery life of the device.

In some embodiments, while displaying the wake screen user interfacewith all of the one or more notifications (e.g., before the userinteracted with one of the notifications or opened an application thatcorresponds to one of the one or more notifications), the device detects(636) a third transitioning from the screen-on state to the screen-offstate (e.g., the transition is triggered when an amount of time that haspassed since a last input was received increased above a threshold time,or when an input is received at a control for shutting off the display)followed by a fourth transition from the screen-off state to thescreen-on state (e.g., when an input is received to wake the device orturn on the display). For example, a transition from the screen-on stateto the screen-off state is shown in FIGS. 5B-5C and a transition fromthe screen-off state to the screen-on state is shown in FIGS. 5C-5D. Inresponse to detecting the third transition followed by the fourthtransition, the device redisplays the wake screen user interface withthe one or more notifications on the wake screen user interface (e.g.,all of the missed notifications still remain on the wake screen). Forexample, in FIG. 5D, all of the notifications 506-512 displayed in FIG.5B are redisplayed.

Maintaining display of a set of missed notifications after a transitionfrom the screen-on state to the screen-off state followed by atransition from the screen-off state to the screen-on state makes theuser-device interface more efficient and enhances the operability of thedevice by allowing a user to display the wake screen repeatedly (e.g.,to view the time or check for an incoming notification) whilemaintaining a list of missed notifications for the user to handle whenthe user is ready to interact with the notifications (without requiringthe user to provide input for redisplaying the missed notificationswhile the wake screen is displayed).

In some embodiments, while displaying the wake screen user interfacewith the one or more notifications, the device detects (638) a tenthinput (e.g., an upward swipe gesture on the touch-sensitive surface) fordisplaying an authentication user interface 518 (e.g., including apassword input prompt, such as a number pad). In response to detectingthe tenth input for displaying the authentication user interface: thedevice ceases to display the wake screen user interface 504 and displaysthe authentication user interface 518. For example, in response to aninput described with regard to FIG. 5E, authentication user interface518 is displayed in FIG. 5F. While the authentication user interface 518is displayed, the device detects an authorization input (e.g., apasscode entered via the number pad). In accordance with a determinationthat the authorization input is valid, the device displays a second userinterface (e.g., an application user interface, a settings userinterface, or a home screen user interface). For example, in response todetecting the authorization input shown in FIG. 5G, home screen userinterface 522 is displayed in FIG. 5H. While displaying the second userinterface, the device detects an eleventh input for redisplaying thewake screen user interface 504 (e.g., detecting a downward swipe gestureon the touch- sensitive surface (e.g., a downward swipe gesture thatstarted from the top edge of the touch-sensitive surface)). In responseto detecting the eleventh input, the device ceases to display the secondapplication user interface; and redisplays the wake screen userinterface with the one or more notifications. For example, an input forredisplaying wake screen user interface 504 received while home screenuser interface 522 is displayed is shown in FIGS. 5I-5J In someembodiments, in accordance with a determination that the authorizationinput is not valid, the second user interface is not displayed and/orthe user is prompted for additional authorization input. In someembodiments, the authentication is automatically performed, anddetecting an upward swipe gesture dismisses the wake screen userinterface and reveals the last active user interface prior to thedevice's transition from the screen-on state to the screen-off state, orthe last active user interface prior to the device's transition from theunlocked state to the locked state.

Maintaining display of a set of missed notifications after detectingintermediate inputs for dismissing and redisplaying a wake screen userinterface makes the user-device interface more efficient and enhancesthe operability of the device by allowing a user to display the wakescreen repeatedly (e.g., to view the time or check for an incomingnotification) while maintaining a list of missed notifications for theuser to handle when the user is ready to interact with the notifications(without requiring the user to provide input for redisplaying the missednotifications while the wake screen is displayed).

In some embodiments, in accordance with the determination that the thirdinput meets the notification-clearance criteria, the device adds (640),to a set of recent notifications, one or more cleared notifications thatcorrespond to the at least one of the one or more notifications notdisplayed on the wake screen user interface. In some embodiments, whenthe notification-clearance criteria are met, all of the missednotifications are cleared from the wake screen user interface/coversheet user interface, and are added to a list of recent notifications.In some embodiments, when a missed notification is individually clearedby direct user interaction with that notification, that notification isadded to the list of recent notifications.

Adding a cleared notification to a set of recent notifications makes thecleared notification available for future user access. Making a clearednotification available for future user access makes the user-deviceinterface more efficient by allowing a user to view notification contentassociated with multiple applications without individually accessingeach application).

In some embodiments, after adding the one or more cleared notificationsto the set of recent notifications, while the wake screen user interfaceis displayed, the device detects (642) a twelfth input (e.g., an upwardswipe on the touch-screen that pulls on a currently displayednotification, or an input on a control for revealing recentnotifications). In response to detecting the twelfth input, inaccordance with a determination that the twelfth input meetsrecent-notification-display criteria, the device displays at least aportion of the set of recent notifications (e.g., overlaid on the wakescreen user interface). For example, In FIGS. 5BJ-5BO, notifications506-512, that were cleared as discussed with regard to 5A-5AW, areredisplayed in response to an input that meetsrecent-notification-display criteria.

Displaying notifications from a set of recent notifications in responseto input on the wake screen user interface allows a user to view asequential list of notification content (e.g., including notificationsthat were previously cleared). Allowing a user to view a sequential listof notification content received by the device makes the user-deviceinterface more efficient by allowing a user to view notification contentassociated with multiple applications without individually accessingeach application).

It should be understood that the particular order in which theoperations in FIGS. 6A-6G have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 700, 800, and 900) are also applicable in an analogous manner tomethod 600 described above with respect to FIGS. 6A-6G. For example, thecontacts, gestures, user interface objects, tactile outputs, focusselectors, and animations described above with reference to method 600optionally have one or more of the characteristics of the contacts,gestures, user interface objects, tactile outputs, focus selectors, andanimations described herein with reference to other methods describedherein (e.g., methods 700, 800, and 900). For brevity, these details arenot repeated here.

The operations described above with reference to FIGS. 6A-6G are,optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, receiving operation 602, detection operation 604, transitioningoperation 606, and displaying operation 606, are, optionally,implemented by event sorter 170, event recognizer 180, and event handler190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

FIGS. 7A-7E are flow diagrams illustrating method 700 of displayingnotification history in accordance with some embodiments. Method 700 isperformed at an electronic device (e.g., device 300, FIG. 3, or portablemultifunction device 100, FIG. 1A) with a display, a touch-sensitivesurface, and one or more sensors to detect intensity of contacts withthe touch-sensitive surface. In some embodiments, the display is atouch-screen display and the touch-sensitive surface is on or integratedwith the display. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 700 are, optionally,combined and/or the order of some operations is, optionally, changed.

As described below, method 700 provides an intuitive way to display anotification history. The method reduces the number, extent, and/ornature of the inputs from a user when displaying a notification history,thereby creating a more efficient human-machine interface. Forbattery-operated electronic devices, enabling a user to display anotification history faster and more efficiently conserves power andincreases the time between battery charges.

The device displays (702), on display 112, a first user interface,including displaying one or more missed notifications in a firstscrollable arrangement (e.g., a first scrollable list) on the first userinterface. For example, in FIG. 5BA, notifications 586, 588, 590, and592 are displayed on wake screen user interface 504. In someembodiments, the first user interface is a wake screen user interface504 that is displayed upon the display transitioning from a display-offstate to a display-on state (e.g., in response to detecting an input orevent that wakes the device from the display-off state, such as a sleepstate or other power-saving or inactive state). For example, FIGS.5A1-5A4 show the display transitioning from a display-off state to adisplay-on state. In some embodiments, the first user interface is acover sheet user interface (also depicted as 504) that is displayed tocover a currently displayed user interface when a downward edge swipegesture (e.g., a downward swipe that starts from an upper edge of thetouch-sensitive surface) is detected on the display. In someembodiments, the cover sheet user interface is also the wake screen userinterface that is displayed when the device transitions from thescreen-off state to the screen-on state.

While displaying the first user interface with the one or more missednotifications, the device detects (704) a first swipe gesture (e.g., asshown in FIGS. 5BF-5BG), including detecting a first contact at alocation on the touch-sensitive surface that corresponds to the firstscrollable arrangement (e.g., as indicated by region 5100), anddetecting first movement of the first contact across the touch-sensitivesurface in a first direction (e.g., upward).

In response to detecting the first swipe gesture, the device scrolls(706) the first scrollable arrangement in accordance with the firstmovement of the first contact (e.g., notifications 586-592 move upwardin response to the input illustrated at FIGS. 5BF-5BG).

After scrolling the first scrollable arrangement in accordance with thefirst movement of the first contact, the device detects (708) a secondswipe gesture, including detecting a second contact at a location on thetouch-sensitive surface that corresponds to the first scrollablearrangement and detecting second movement of the second contact acrossthe touch-sensitive surface in the first direction (e.g., as shown inFIGS. 5BI-5BN).

In response to detecting the second swipe gesture (710): in accordancewith a determination that the second movement of the second contactmeets notification-history-display criteria, the device displays aplurality of previously received notifications that are distinct fromthe one or more missed notifications in a second scrollable arrangementon the first user interface (e.g., the device displays previouslyreceived notifications 506-512, which are distinct from missednotifications 586-592). The notification-history-display criteriarequire (1) that the second movement of the second contact is detectedafter an end (e.g., a bottommost missed notification 5102) of the firstscrollable arrangement has been reached in accordance with the firstmovement of the first contact and (2) that the second movement exceeds afirst threshold amount of movement (e.g., as indicated at 5108) in thefirst direction. In accordance with the determination that the secondmovement of the first contact does not meet thenotification-history-display criteria, the device forgoes displaying theplurality of previously received notifications (and, optionally,continuing to scroll the first scrollable arrangement in accordance withthe second movement of the second contact).

This method relates to a way to combine the functions of a wake screenuser interface and a notification history screen into a wake screen userinterface. The wake screen user interface displays missed notifications,and in response to specific inputs notification history is displayed inthe wake screen user interface as well. Displaying previously receivednotifications in accordance with a determination that movement of acontact meets notification history display criteria allows a user toview a sequential list notification content received by the device(e.g., including notifications that were previously cleared). Thenotifications in the second scrollable arrangement remain undisplayedwhen swipe input does not meet the notification-history-displaycriteria, so that the user does not unintentionally reveal previouslycleared notifications. Allowing a user to view a sequential list ofnotification content received by the device makes the user-deviceinterface more efficient by allowing a user to view notification contentassociated with multiple applications without individually accessingeach application. Leaving the notifications in the second scrollablearrangement undisplayed when swipe input does not meet thenotification-history-display criteria allows the user to navigate amongthe missed notifications in the first scrollable arrangement withoutunintentionally viewing previously cleared notifications.

In some embodiments (712), the first user interface is a wake screenuser interface 504, and the first user interface is displayedimmediately upon waking the device from the display-off state to thedisplay-on state. For example, FIGS. 5A1-5A4 show display of a wakescreen user interface 504 when device 100 transitions from a display-offstate to a display-on state.

In some embodiments, while displaying the one or more missednotifications in the first scrollable arrangement on the first userinterface, the device detects (714) a missed notification dismissalinput for dismissing a respective notification of the one or more missednotifications in the first scrollable arrangement. For example, input todismiss notification 592 is illustrated in FIGS. 5BV-5BY. A dismissalinput for dismissing a respective notification is, e.g., an input toactivate a displayed control (e.g., a tap gesture by a contact at alocation that corresponds to the displayed control) for dismissing thenotification; an input (such as a deep press or swipe gesture) on thenotification to dismiss the notification, or to reveal a control fordismissing the notification followed by an input to activate a controlfor dismissing the notification, or an input to open the notification inan application(e.g., a tap gesture by a contact at a location thatcorresponds to the notification)). After detecting the missednotification dismissal input for dismissing the respective notification,the device ceases to display the respective notification of the one ormore notifications on the first user interface, and adds the respectivenotification to the plurality of previously received notifications. Forexample, if the wake screen is displayed again without the respectivenotification, and a swipe gesture that meetsnotification-history-display criteria is detected on the first scrollarrangement including the remaining missed notifications, the respectivenotification is displayed among the plurality of previously receivednotifications in the second scrollable arrangement.

Ceasing to display a notification after detecting a missed notificationdismissal input for dismissing the notification reduces the number ofnotifications displayed on the first user interface after the user hasprovided input that indicates the notification has been viewed and/orhandled by the user. Reducing the number of notifications displayed onthe first user interface makes the user-device interface more efficientby allowing a user to more quickly locate and address notifications thathave not been previously viewed and/or handled by the user.

In some embodiments, while the first user interface is displayed, thedevice detects (716) a third swipe gesture (e.g., as shown at FIGS.5BB-5BC), including detecting a third contact at a location on thetouch-sensitive surface that corresponds the first scrollablearrangement and detecting third movement of the third contact across thetouch-sensitive surface in a second direction that is distinct from thefirst direction (e.g., downwards). In response to detecting the thirdswipe gesture, the device translates the first scrollable arrangement(and optionally, at least one object (e.g., an object that displays acurrent time and/or date)) in accordance with the third movement of thethird contact (e.g., translating the first scrollable arrangementrelative to other objects currently displayed on the first userinterface in the downward direction, or translating the first userinterface as a whole in the downward direction to display an extensionof the first user interface at the top that was not displayed prior todetecting the third swipe gesture). For example, notifications 586-592move downward in accordance with the movement of the input shown inFIGS. 5BB-5BC. The device detects lift-off of the third contact from thetouch-sensitive surface (e.g., the touch-screen display) after detectingthe third movement (e.g., the contact indicated by focus selector 594 inFIG. 5BC has lifted off of touch screen 112, as shown in FIG. 5BD). Inresponse to detecting the liftoff of the third contact, the devicereverses the translation of the first scrollable arrangement that wasmade in accordance with the third movement of the third contact (e.g.,restoring the position of the first scrollable arrangement relative tothe other objects currently displayed on the first user interface, orrestoring the first user interface as a whole and ceasing to display theextension of the first user interface at the top). As shown in FIGS.5BD-5BE, in response to the liftoff that occurred, the notificationsmove 586-592 upward.

Providing visual feedback, such as a “rubber band effect” simulated bytranslating the scrollable arrangement of missed notifications inaccordance with movement of a contact and reversing the translation ofthe scrollable arrangement upon lift-off of the contact, enhancesoperability of the device by providing an intuitive indication to theuser that the first user interface is responsive to input (such as aswipe input) to view additional notifications.

In some embodiments, while displaying the plurality of previouslyreceived notifications in the second scrollable arrangement on the firstuser interface, the device detects (718) a fourth swipe gesture (e.g.,as shown at FIG. 5CA), including detecting a fourth contact at alocation on the touch-sensitive surface that corresponds to the secondscrollable arrangement (e.g., notifications 506-512) and detectingfourth movement of the fourth contact across the touch-sensitive surfacein a second direction opposite the first direction (e.g., the fourthswipe gesture is a downward swipe gesture directed to the secondscrollable arrangement). In response to detecting the fourth swipegesture, in accordance with a determination that the fourth movement ofthe fourth contact meets notification-history-dismissal criteria, thedevice ceases to display the plurality of previously receivednotifications on the first user interface. In some embodiments, thenotification-history-dismissal criteria require (1) that the fourthmovement of the fourth contact is detected after an end (e.g., anuppermost notification) of the second scrollable arrangement has beenreached and (2) that the fourth movement exceeds a second thresholdamount of movement in the second direction opposite the first direction.In accordance with the determination that the fourth movement of thefourth contact does not meet the notification-history-dismissalcriteria, the device scrolls the plurality of previously receivednotifications in the second scrollable arrangement in accordance withthe fourth movement of the fourth contact. In some embodiments,scrolling the plurality of previously received notifications in thesecond scrollable arrangement causes at least one of the one or moremissed notifications in the first scrollable arrangement to be revealed(e.g., if the at least one of the one or more missed notifications inthe first scrollable arrangement was scrolled beyond the edge of thedisplay in response to the first swipe gesture and/or the second swipegesture). In some embodiments, scrolling previously receivednotifications causes missed notifications in the first scrollablearrangement to be revealed (e.g., as shown in FIGS. 5BT-5BU), allowing auser to navigate between notifications that have been cleared andnotifications that have not yet been cleared for a comprehensive view ofnotifications that have been received by the device. Providing the userwith a comprehensive view of notifications that have been received bythe device makes the user-device interface more efficient by allowing auser to view recent notification content without needing to individuallyaccess each application for which the content was received and/orgenerated.

Scrolling through the notification history or dismissing thenotification history based on the same swipe gesture in accordance withwhether the notification-history-dismissal criteria are met enhances theoperability of the user interface and makes the user-device interfacemore efficient (e.g., by performing different functions based on whetherpredefined conditions are met), which additionally improves the batterylife of the device.

In some embodiments, while displaying the first user interface, thedevice detects (720) a first user interface dismissal input for input(e.g., as shown at FIG. 5CO) for dismissing the first user interface(e.g., a swipe gesture, including fifth movement of a fifth contact froma location that corresponds to an edge of the display (such as alocation that is at or proximate to the bottom edge of the display)across the touch-sensitive surface in the first direction (e.g., upwardfrom the bottom edge of the display). In response to detecting the firstuser interface dismissal input, the device ceases to display the firstuser interface (e.g., along with any missed notifications and/or recentnotifications that are currently displayed on the first user interface),and, in some embodiments, the device reveals an underlying interfacesuch as a home screen user interface 522, a settings user interface, oran application user interface. For example, in FIGS. 5CO-5CQ, homescreen user interface 522 is revealed in response to an input fordismissing wake screen user interface 504.

In some embodiments, the device includes one or more tactile outputgenerators (722), and while the first user interface is displayed, inaccordance with the determination that the second movement of the secondcontact meets the notification-history-display criteria (e.g., asdescribed with regard to FIG. 5BK), the device generates, with the oneor more tactile output generators, a tactile output (e.g., tactileoutput 5112) to indicate that the criteria for displaying the pluralityof previously received notifications have been met.

Generating a tactile output to indicate that criteria for displaying theplurality of previously received notifications have been met providesthe user with feedback about the input that is required to meetnotification-history-display criteria. Providing the user with feedbackabout the input that is required to meet notification-history-displaycriteria makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments (724), the first contact moves with a first rate ofmovement during the first swipe gesture, scrolling the first scrollablearrangement occurs at a first scroll rate that corresponds to the firstrate of movement by the first contact (e.g., the scroll rate matches thefirst rate of movement); the second contact moves with a second rate ofmovement during the second swipe gesture; and displaying the pluralityof previously received notifications in the second scrollablearrangement includes scrolling a first previously received notificationof the plurality of previously received notifications in the secondscrollable arrangement at a second scroll rate that is greater than thesecond rate of movement by the second contact (e.g., to provide anappearance of the previously received notifications in the secondscrollable arrangement “catching up” with the second contact). Forexample, as the contact indicated by focus selector 5106 moves alongtouch screen 112 as shown in FIGS. 5BI-5BN, missed notifications 586-592in a first scrollable arrangement move at the rate of movement of thecontact, and, in FIGS. 5BK-5BN, previously received notifications506-512 in a second scrollable arrangement move faster than the rate ofmovement of the contact. In some embodiments, a second previouslyreceived notification of the plurality of previously receivednotifications is scrolled at a third scroll rate that is distinct fromthe second scroll rate.

Scrolling a first previously received notification of the plurality ofpreviously received notifications in the second scrollable arrangementat a second scroll rate that is greater than the second rate of movementby the second contact provides the user with visual feedback about theinput that is required to meet notification-history-display criteria(e.g., by giving the user of a sense of the notifications in the secondscrollable arrangement “racing to catch up” with the second contact whenthe criteria are met). Providing the user with feedback about the inputthat is required to meet notification-history-display criteria makes theuser-device interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the device detects (726) a fifth swipe gesture,including detecting a fifth contact at a first location on thetouch-sensitive surface and detecting fifth movement of the fifthcontact across the touch-sensitive surface in a third direction that isperpendicular to the first direction (e.g., leftward or rightward). Inresponse to detecting the fifth swipe gesture, in accordance with adetermination that the first location on the touch-sensitive surfacecorresponds to a first notification among the one or more missednotifications or the plurality of previously received notifications, thedevice moves the first notification in accordance with the movement ofthe fifth contact (e.g., the input shown in FIG. 5BV-5BW dragsnotification 592). In accordance with a determination that the firstlocation on the touch-sensitive surface corresponds to a locationoutside of the first scrollable arrangement and the second scrollablearrangement, the device replaces display of the first user interfacewith display of a second user interface (e.g., a control center userinterface 5138 or mini application user interface 5140). For example,FIGS. 5CC-5CE illustrate a swipe gesture by contact at a locationoutside of the first scrollable arrangement and the second scrollablearrangement that causes control center user interface 5138 to bedisplayed, and FIGS. 5CI-5CK illustrate a swipe gesture by contact at alocation outside of the first scrollable arrangement and the secondscrollable arrangement that causes mini application user interface 5140to be displayed.

This heuristic allows a swipe gesture (e.g., a horizontal swipe gesture)to have different responses depending on whether the gesture correspondsto a missed notification or corresponds to a location outside ofscrollable arrangements of missed notifications. This heuristic enhancesoperability of the device by providing different responses to the samegesture depending on the location of the gesture rather than requiringthe device to provide a different gesture type (in turn requiring theuser to learn the additional gesture type) to obtain the differentresponses.

In some embodiments, the device detects (728) that criteria fordismissing all of the one or more missed notifications in the firstscrollable arrangement are met (e.g., via one or more inputs thatinclude user interaction with all of the missed notifications, via oneor more inputs for accessing one or more applications associated withthe missed notifications, and/or by satisfying notification clearancecriteria that require input that is received at a time that is (1) aftera respective notification of the one or more notifications has beencleared through direct user interaction with the respective notificationor an application that corresponds to the respective notification and(2) after the device has transitioned from the screen-on state to thescreen-off state at least once since the last direct user interactionthat dismissed a respective notification). In response to detecting thatthe criteria for dismissing all of the one or more missed notificationsare met, the device adds, to the plurality of previously receivednotifications, all of the one or more missed notifications (and forgoingdisplaying those one or more missed notifications the next time that thefirst user interface is displayed). For example, in FIG. 5CS, allnotifications have been cleared (e.g., as a result of input as shown atFIGS. 5BV-5BZ and FIGS. 5CQ-5CS). In FIG. 5CX, in response to inputshown in 5CW, notifications 586-592 that had been cleared and added tothe plurality of previously received notifications are redisplayed.

In some embodiments, while displaying the first user interface withoutany missed notifications (e.g., after detecting that the criteria fordismissing all of the one or more missed notifications in the firstscrollable arrangement have been met and adding the one or more missednotifications to the plurality of previously received notifications),the device detects (730) a sixth swipe gesture (e.g., as shown in FIG.5CW), including a sixth contact at a location on the touch-sensitivesurface that corresponds to the location at which the first scrollablearrangement was previously displayed, and the device detects sixthmovement of the sixth contact across the touch-sensitive surface in thefirst direction. In response to detecting the sixth swipe gesture: inaccordance with a determination that the sixth movement of the sixthcontact exceeds the first threshold amount of movement in the firstdirection, the device displays the plurality of previously receivednotifications (including the one or more missed notifications that weredismissed and added to the plurality of previously receivednotifications). For example, in FIG. 5CX, in response to input shown in5CW, notifications 586-592 are redisplayed. In accordance with thedetermination that the sixth movement of the sixth contact does notexceed the first threshold amount of movement in the first direction,the device forgoes displaying the plurality of previously receivednotifications.

Displaying a plurality of previously received notifications afterdisplaying the first user interface without any missed notificationsallows a user to recall missed notifications (e.g., even after providinginput to clear all missed notifications). Enabling the user to recallthe missed notifications makes the user-device interface more efficientand by allowing the user to view content received and/or generated bythe device without needing to access multiple applications.Additionally, a user can provide input to clear notifications with theknowledge that the notification will be recoverable if the usersubsequently wishes to view the notification content.

In some embodiments, while the first user interface is displayed withoutany missed notifications (e.g., after detecting that the criteria fordismissing all of the one or more missed notifications in the firstscrollable arrangement have been met and adding the one or more missednotifications to the plurality of previously received notifications),the device detects (732) a seventh swipe gesture (e.g., as shown atFIGS. 5CS-5CT), including detecting a seventh contact at a location onthe touch-sensitive surface that corresponds to the location at whichthe first scrollable arrangement was previously displayed and detectingseventh movement of the seventh contact across the touch-sensitivesurface in a second direction opposite the first direction (e.g.,downward). In response to detecting the seventh swipe gesture, thedevice translates at least one object (e.g., an object 582 that displaysa current time and/or date) displayed on the first user interface in thesecond direction in accordance with the seventh movement of the seventhcontact. After translating the at least one object, the device detectslift-off of the seventh contact (e.g., as shown at FIG. 5CU). Inresponse to detecting liftoff of the seventh contact from thetouch-sensitive surface, the device reverses the translation of the atleast one object that have been made in accordance with the seventhmovement of the seventh contact.

Providing visual feedback, such as a “rubber band effect” simulated bytranslating at least one object in accordance with movement of a contactand reversing the translation of the at least one object upon lift-offof the contact, enhances operability of the device by providing anintuitive indication to the user that the wake screen is responsive toinput (such as a swipe input) to view notifications (e.g., even when theuser is viewing a first user interface that does not include display ofany missed notifications).

It should be understood that the particular order in which theoperations in FIGS. 7A-7E have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 600, 800, and 900) are also applicable in an analogous manner tomethod 700 described above with respect to FIGS. 7A-7E. For example, thecontacts, gestures, user interface objects, tactile outputs, focusselectors, and animations described above with reference to method xxxoptionally have one or more of the characteristics of the contacts,gestures, user interface objects, tactile outputs, focus selectors, andanimations described herein with reference to other methods describedherein (e.g., methods 600, 800, and 900). For brevity, these details arenot repeated here.

The operations described above with reference to FIGS. 7A-7E are,optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, display operation 702, detection operation 704, and scrollingoperation 706 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

FIGS. 8A-8C are flow diagrams illustrating method 800 of displayingupdating information from an application using a floating banner inaccordance with some embodiments. Method 800 is performed at anelectronic device (e.g., device 300, FIG. 3, or portable multifunctiondevice 100, FIG. 1A) with a display, a touch-sensitive surface, and oneor more sensors to detect intensity of contacts with the touch-sensitivesurface. In some embodiments, the display is a touch-screen display andthe touch-sensitive surface is on or integrated with the display. Insome embodiments, the display is separate from the touch-sensitivesurface. Some operations in method 800 are, optionally, combined and/orthe order of some operations is, optionally, changed.

As described below, method 800 provides an intuitive way to displayupdating information from an application in a floating banner. Themethod reduces the number, extent, and/or nature of the inputs from auser when accessing information that is displayed in the floatingbanner, thereby creating a more efficient human-machine interface. Forbattery-operated electronic devices, displaying updating informationfrom an application in floating banner that is visible in variousoperating contexts allows the user to operate the device faster and moreefficiently, which conserves power and increases the time betweenbattery charges.

The device displays (802) a first user interface (e.g., an applicationuser interface, a home screen user interface, a lock screen userinterface, etc.) on the display. For example, in FIG. 5DA, the devicedisplays a map application user interface 5154.

The device displays (804) a first user interface object overlaid on afirst portion of the first user interface (e.g., the device displays abanner object, such as navigation banner 5160, overlaid on a userinterface of an application, such as map application user interface5154), where the banner object is initially stationary relative to theuser interface of the application. In some embodiments, the first userinterface object is displayed when a persistent banner display mode ofan application is active. In some embodiments, persistent banner displaymodes include a navigation mode of a maps application, and the firstuser interface object is a banner that includes navigation information,such as text and/or an icon indicating information associated with anext step in a navigation sequence (e.g., navigation informationincludes navigation text 5178 and navigation direction image 5180, asshown in FIG. 5DT). In some embodiments, persistent banner display modesinclude a content playback mode of a media application, and the firstuser interface object is a banner that includes media playbackinformation, such as text and/or an image that correspond to a playingcontent item and/or one or more playback controls (see, e.g., mediabanner 568 shown in FIG. 5AO). In some embodiments, persistent bannerdisplay modes include a telephone call session of a telephoneapplication, and the first user interface object is a banner thatincludes text with information about the call in progress, such aselapsed time and/or contact information. In some embodiments, the firstuser interface object is a notification.

While displaying the first user interface object overlaid on the firstportion of the first user interface, the device detects (806) a firstinput (e.g., a downward swipe input from an upper edge of the display112, as shown at FIG. 5DB) for displaying a cover sheet user interface504. In some embodiments, the cover sheet user interface 504 is also awake screen user interface that is displayed when the device transitionsfrom a screen-off state to a screen-on state. The cover sheet userinterface 504 includes a first content object (e.g., one or more missednotifications, such as missed notifications 5164 and 5168 shown in FIG.5DD) and a second content object (e.g., a time-date object 582 thatdisplays a current time and date) displayed on a background object(e.g., a cover sheet platter or substrate with a predefined background).

In response to detecting the first input for displaying the cover sheetuser interface 504, the device moves (808) the cover sheet userinterface 504 across the display in a first direction (e.g., downward).For example, cover sheet user interface 504 slides down over mapapplication user interface 5154, as shown at FIGS. 5DC-5DD. Moving thecover sheet user interface 504 across the display in a first directionincludes moving the background object 5163 of the cover sheet userinterface 504 across the display (e.g., to obscure an increasing portionof the first user interface without obscuring the first user interfaceobject that is overlaid on the first user interface). In someembodiments, the background object 5163 of the cover sheet userinterface slides onto the display in a z-layer that is located betweenthe z-layer of the first user interface and the z-layer of the firstuser interface object.

Many electronic devices display user interface objects that have a layerorder (i.e., a z-order or front-to-back order of the user interfaceobjects). A user typically interacts with such objects by repositioningthem on the display, and overlapping objects are displayed on thedisplay in accordance with their front-to-back order (e.g., an objectthat is “in front” of another object is displayed where the two objectsoverlap). As used in the specification, a “layer order” is thefront-to-back order of objects in a user interface (e.g., in anelectronic document). Thus, if two objects overlap, the object that ishigher in the layer order (e.g., the object that is “on top of” or “infront of”) is displayed at any points where the two objects overlap,thereby partially obscuring the object that is lower in the layer order(e.g., the object that is “beneath” or “behind” or “in back of” theother object).

In accordance with a determination that the first user interface objecthas not reached a predefined threshold position relative to the coversheet user interface (e.g., relative to a position between the firstcontent object (e.g., missed notifications 5164 and/or 5168) and thesecond content object (e.g., time/date object 582) in the cover sheetuser interface 504), the device moves the first content object and thesecond content object (e.g., in unison) with the background object 5163while maintaining a current position of the first user interface object(e.g., navigation banner 5160) on the display (e.g., as shown in FIGS.5DC-5DD). In accordance with a determination that the first userinterface object (e.g., navigation banner 5160) has reached thepredefined threshold position relative to the cover sheet userinterface, the device moves the first user interface object (e.g., inunison) with the background object (e.g., as shown in FIGS. 5DD-5DE). Insome embodiments, the device also moves the first content object (e.g.,missed notifications 5164 and 5168), the second content object (e.g.,time/date object 582), and the first user interface object (e.g.,navigation banner 5160) in unison with the background object 5163. Forexample, in FIG. 5DD, the time/date object 582 catches the banner object5160 on its way down and pushes the banner object downward with thetime/date object.

Method 800 relates to combining display of a user interface object thatis overlaid on an initial user interface (e.g., a home screen userinterface) with a newly displayed user interface (e.g., a cover sheetuser interface). Specifically, some of the objects on the newlydisplayed user interface move past the first user interface object,while other objects on the newly displayed user interface “catches” thefirst user interface object and pushes it to its final position on thenewly displayed user interface. This heuristic brings attention to thefirst user interface object (e.g., a banner object) by moving or notmoving the first user interface object with the background objectdepending on whether the first user interface object has reached apredefined threshold position relative to a cover sheet interface.Bringing attention to the first user interface object improves theuser-device interface, e.g., by helping the user to understand theconnection between the banner content and the application from which thebanner content originated. Displaying the banner improves theoperability of the device by allowing the user to view content from anapplication without needing to navigate to the application, reducing thenumber of inputs required from the user to obtain banner content (e.g.,navigation information).

In some embodiments, moving the cover sheet user interface 504 acrossthe display in the first direction includes (810), in accordance with adetermination that the second content object (e.g., the time and dateobject 582) has reached a first predefined location (e.g., the defaultposition for the time and date on the display when the cover sheet isfully displayed) on the display, ceasing to move the second contentobject (e.g., the time and date 582) and the first user interface object(e.g., the banner 5160) and continuing to move the first content object(the one or more missed notifications) in the first direction (e.g., tomake room for the banner object 5160 between the top missednotifications (e.g., notifications 5164 and 5168) and the current timeand date object 582. For example, as cover sheet user interface 504slides down in FIGS. 5DC-5DF, time/date object 582 and the navigationbanner 5160 stop moving in FIG. 5DE, while missed notifications 5164 and5168 continue to move downward in FIGS. 5DE-5DF.

Ceasing to move some of the content object while continuing to moveother content objects on the cover sheet user interface allows the coversheet user interface to be rearranged to accommodate the first userinterface object (e.g., the banner), while providing visual continuityto the user, thereby reducing user mistakes when operating the deviceand enhance the operability of the device.

In some embodiments, the device ceases (812) to continue to move thefirst content object (e.g., the one or more missed notifications) in thefirst direction in accordance with a determination that the firstcontent object has reached a second predefined location on the display(e.g., ceasing to move the missed notifications once the missednotifications have completely moved past the banner object).

Continuing to move the content objects on the cover sheet user interfaceuntil they reach their final locations allows the cover sheet userinterface to be rearranged to accommodate the first user interfaceobject (e.g., the banner), while providing visual continuity to theuser, thereby reducing user mistakes when operating the device andenhance the operability of the device.

In some embodiments, the device transitions (814) from a screen-on state(as shown in FIG. 5DY) to a screen-off state (as shown in FIG. 5DZ) inaccordance with a determination that display shutoff criteria are met(e.g., a power button is pressed or a period of user inactivity isdetected). While the display is in the screen-off state, the devicedisplays the first user interface object (e.g., the banner 5160) on adark screen corresponding to the screen-off state (e.g., in accordancewith a determination that an application associated with the first userinterface object is in a persistent banner display mode, such as anavigation mode of a map application, a playback mode of a mediaapplication, or a call mode of a phone application). For example, inFIG. 5DZ, navigation banner 5160 is displayed on an otherwise darkdisplay 112.

Displaying a first user interface object (e.g., a banner) when thedevice is in a screen-off state (e.g., displaying the first userinterface object on an otherwise dark screen or on a screen thatdisplays only one or more received notifications in addition to thefirst user interface object) provides the user with high priorityinformation (e.g., navigation information) while the display forgoesdisplaying other content. Displaying the first user interface object(and/or the one or more missed notifications) while forgoing display ofother content makes the user-device interface more efficient by reducingthe amount of power required for the display. Additionally, displayingthe first user interface object (and/or the one or more missednotifications) while forgoing display of other content eliminates theneed for the user to wake the display from a screen-off state to displaythe first user interface object.

In some embodiments, while the display is in the screen-off state andthe first user interface object is displayed on the display, the devicereceives (816) one or more notifications and, in response to receivingthe one or more notifications, the device displays the first userinterface object (e.g., the banner) and a third content object (e.g.,the one or more notifications) on the first user interface (e.g., theone or more missed notifications are displayed under the first userinterface object). For example, in FIG. 5EA, the device displays banner5160 and missed notification 5186 on otherwise dark display 112. In someembodiments, while the display is in the screen-off state, the devicedetects a notification event and displays a notification object (e.g.,for a new notification) under the banner. In some embodiments, one ormore previously received notifications are displayed on the display(e.g., under the banner and/or above the new notification) while thedisplay is in the screen-off state.

Displaying one or more received notifications when the device is in ascreen-off state (e.g., displaying the one or more receivednotifications on an otherwise dark screen or on a screen that displaysonly a first user interface object in addition to the one or morereceived notifications) provides the user with high priority information(e.g., navigation information) while the display forgoes displayingother content. Displaying the one or more received notifications (and/orthe first user interface object) while forgoing display of other contentmakes the user-device interface more efficient by reducing the amount ofpower required for the display. Additionally, displaying the one or moremissed notifications (and/or the first user interface object) whileforgoing display of other content eliminates the need for the user towake the display from a screen-off state to display the one or moremissed notifications.

In some embodiments, the device transitions (818) the device from ascreen-off state to a screen-on state (e.g., as shown in FIGS. 5A1-5A3and 5EA-5EB) in accordance with a determination that display-wakingcriteria are met (e.g., a power button is pressed or the deviceorientation is changed in a certain way (e.g., picked up by a user), ora notification event is detected). In response to transitioning thedevice from the screen-off state to the screen-on state, the devicedisplays the first user interface object (and no other objects) on adark screen that corresponds to the display-off state. For example, inFIG. 5DZ, navigation banner 5160 is displayed on an otherwise darkdisplay 112.

Displaying a first user interface object (e.g., a banner) when thedevice is in a screen-off state (e.g., displaying the first userinterface object on an otherwise dark screen or on a screen thatdisplays only one or more received notifications in addition to thefirst user interface object) provides the user with high priorityinformation (e.g., navigation information) while the display forgoesdisplaying other content. Displaying the first user interface object(and/or the one or more missed notifications) while forgoing display ofother content makes the user-device interface more efficient by reducingthe amount of power required for the display. Additionally, displayingthe first user interface object (and/or the one or more missednotifications) while forgoing display of other content eliminates theneed for the user to wake the display from a screen-off state to displaythe first user interface object.

In some embodiments, while the cover sheet interface is displayed, thedevice detects (820) a third input (e.g., as shown at FIGS. 5DQ-5DR) fordismissing the cover sheet user interface 504. The third input includesa swipe gesture by a contact on the touch-sensitive surface (e.g., aupward swipe that started from the bottom edge of the touch-screen). Inresponse to detecting the third input for dismissing the cover sheetuser interface, the device ceases to display the cover sheet userinterface 504, maintains display of the first user interface object(e.g., navigation banner 5160), and displays a home screen userinterface 522. The first user interface object is overlaid on the homescreen user interface. For example, in response to detecting an upwardswipe gesture from the bottom edge of the touch-screen (e.g., as shownin FIGS. 5DQ-5DR), the cover sheet user interface 504 slides upward toreveal the home screen interface 522 underneath, while the first userinterface (e.g., navigation banner 5160) remains stationary in a displaylayer above the cover sheet user interface 504, and appears overlaid onthe home screen user interface 522 after the cover sheet user interface504 is completely removed from view. In some embodiments, instead of thehome screen user interface 522, a user interface of an application isdisplayed when the input for dismissing the cover sheet user interface504 is detected, and the first user interface object is overlaid on theuser interface of the application.

Displaying the first user interface object (e.g., a banner, such asnavigation banner 5160) overlaid on the home screen makes theuser-device interface more efficient by allowing the user to view thefirst user interface object after accessing the home screen withoutneeding to navigate from the home screen to the application thatgenerated the content of the first user interface object.

In some embodiments, while displaying the first user interface objectoverlaid on the home screen user interface (or a user interface of anapplication), the device detects (822) an input for minimizing the firstuser interface object (e.g., a upward swipe gesture on the banner, asshown at FIG. 5DT). In response to detecting the input for minimizingthe first user interface object, the device transitions the first userinterface object (e.g., banner mode of navigation banner 5160, as shownin FIG. 5DT) into a second user interface object (e.g., a “pill” thathas a smaller area than the first user interface object, as shown at5160 FIG. 5DW). The first user interface object has a first size and thesecond user interface object has a second size that is smaller than thefirst size. In some embodiments, the second user interface objectpulsates or blinks (e.g., at least a portion of the pill, such as thebackground of the pill, periodically changes color and/or size overtime) to indicate that an application mode or process associated withthe banner object is still active. In some embodiments, the second userinterface object displays at least a portion of information displayed bythe first user interface object. For example, in FIG. 5DT, navigationbanner 5160 in banner mode displays navigation direction arrow 5180,which is also displayed in the pill mode of navigation banner 5160 inFIG. 5DW. In some embodiments, the device displays an animatedtransition showing the banner shrinking and morphing into the “pill”while moving and settling into a upper corner of the touch-screen (e.g.,as shown at FIGS. 5DT-5DW). In some embodiments, the second userinterface object (e.g., navigation banner 5160 in pill form) displaysmedia playback information (e.g., a play/pause toggle control). In someembodiments, the second user interface object displays information(e.g., a turn icon) associated with a navigation instruction.

Transitioning the first user interface object into a second userinterface object in response to detecting input for minimizing the firstuser interface object makes the user-device interface more efficient byallowing the user to simultaneously view content of the home screen userinterface that would otherwise be covered by the first user interfaceobject and information from the first user interface object that iscontained in the second user interface object (e.g., without needing tonavigate from the home screen to the application that generated thecontent of the first user interface object).

In some embodiments, while the second user interface object isdisplayed, the device determines (824) that the display shutoff criteriaare met. In response to determining that the display shutoff criteriaare met, the device transitions the device from the screen-on state to ascreen-off state, transitions the second user interface object into thefirst user interface object; and displays the first user interfaceobject overlaid a dark screen corresponding to the screen-off state(e.g., a direct transition from FIG. 5DX to FIG. 5DZ).

Transitioning the second user interface object into a first userinterface object in response to determining that display shutoffcriteria are met provides the user with a larger object for increasedvisibility when the device is likely to be distant from the user (e.g.,on a table or in a car rather than in the user's hand). Providing theuser with a larger object for increased visibility reduces power usageand improves battery life by providing information without requiring theuser to wake the device and/or navigate to an application that generatedthe content of the first user interface object.

In some embodiments, while the second user interface object isdisplayed, the device detects (826) an input for activating the seconduser interface object (e.g., a tap input on the second user interfaceobject). For example, in FIG. 5DX, an input is detected at a locationcorresponding to navigation banner 5160 in pill form, as indicated byfocus selector 5160 in FIG. 5DX. In response to detecting the input foractivating the second user interface object, the device displays anapplication user interface of an application that corresponds to thesecond user interface object. For example, in response to the inputdescribed with regard to FIG. 5DX, map application 5154 is displayed, asshown in FIG. 5DY.

Displaying an application user interface of an application thatcorresponds to the second user interface object in response to detectinginput for activating the second user interface object provides the userwith direct access to an application that corresponds to the second userinterface object (e.g., the user can access the application thatcorresponds to the second user interface object from any page of amulti-page home screen without needing to provide input to navigate toan application launch icon on a different page of the home screen,within a folder on the home screen, etc.). This makes the user-deviceinterface more efficient and enhances the operability of the device byreducing the number of inputs required to access an application userinterface of an application that corresponds to the second userinterface object.

In some embodiments, while the first user interface object is displayed(e.g., overlaid over the first user interface or overlaid over the coversheet user interface 504), the device detects (828) an input thatactivates the first user interface object (e.g., a tap input on thefirst user interface object). For example, in FIG. 5DH, an input, asindicated by focus selector 5168, is detected at a location thatcorresponds to the navigation object 5160 displayed overlaid over coversheet user interface 504. In response to detecting the input thatactivates the first user interface object, the device displays theapplication user interface of the application that corresponds to theinformation displayed in the first user interface object. For example,in response to the input, maps application 5154 is displayed, as shownin FIG. 5DI.

In some embodiments, the application that corresponds to the second userinterface object is an application that also corresponds to the firstuser interface object.

Displaying an application user interface of an application thatcorresponds to the first user interface object in response to detectinginput for activating the first user interface object provides the userwith direct access to an application that corresponds to the first userinterface object (e.g., the user can access the application thatcorresponds to the first user interface object directly from the firstuser interface or the cover sheet user interface without providing inputto navigate to the home screen.) This makes the user-device interfacemore efficient and enhances the operability of the device by reducingthe number of inputs required to access an application user interface ofan application that corresponds to the first user interface object.

It should be understood that the particular order in which theoperations in FIGS. 8A-8C have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,600, 700, and 900) are also applicable in an analogous manner to method800 described above with respect to FIGS. 8A-8C. For example, thecontacts, gestures, user interface objects, focus selectors, animationsdescribed above with reference to method xxx optionally have one or moreof the characteristics of the contacts, gestures, user interfaceobjects, focus selectors, animations described herein with reference toother methods described herein (e.g., methods 600, 700, and 900). Forbrevity, these details are not repeated here.

The operations described above with reference to FIGS. 8A-8C are,optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, display operation 802, detection operation 806, and objectmoving operation 808 are, optionally, implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

FIGS. 9A-9C are flow diagrams illustrating method 900 of navigationusing a cover sheet, in accordance with some embodiments. Method 900 isperformed at an electronic device (e.g., device 300, FIG. 3, or portablemultifunction device 100, FIG. 1A) with a display, a touch-sensitivesurface, and one or more sensors to detect intensity of contacts withthe touch-sensitive surface. In some embodiments, the display is atouch-screen display and the touch-sensitive surface is on or integratedwith the display. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 800 are, optionally,combined and/or the order of some operations is, optionally, changed.

As described below, method 900 provides an intuitive way to navigateusing a cover sheet. The method reduces the number, extent, and/ornature of the inputs from a user for accessing various controls that areavailable from user interfaces that are accessible via input provided atthe cover sheet, thereby creating a more efficient human-machineinterface. For battery-operated electronic devices, enabling a user tonavigate using a cover sheet faster and more efficiently conserves powerand increases the time between battery charges.

While the device is in a screen-off state, the device detects (902) afirst input for waking the device from the screen-off state to ascreen-on state (e.g., the device detects a state change indicating thatthe device has been picked up, as described with regard to FIGS.5EC1-5EC4, or the device detects an input at a control, such as pushbutton 106, for waking the device).

In response to detecting the first input for waking the device from thescreen-off state to the screen-on state, the device transitions (904)the device from the screen-off state to the screen-on state (e.g., asshown at FIGS. 5EC2-5EC3), and displays a wake screen user interface 504on the display 112. In some embodiments, the wake screen user interface504 is redisplayed as a cover sheet user interface that covers anexisting user interface in response to a cover sheet call-up command,and re-reveals the existing user interface that was covered by the coversheet user interface in response to a cover-sheet dismissal command.

While displaying the wake screen user interface, the device detects(906) a first swipe gesture on the touch-sensitive surface 112 (e.g., aswipe gesture as shown at FIGS. 5EK-5EL or a swipe gesture as shown atFIGS. 5EQ-5ER), including detecting a first contact on thetouch-sensitive surface and detecting movement of the first contactacross the touch-sensitive surface.

In response to detecting the first swipe gesture, the device (908)ceases to display the wake screen user interface 504 and displays afirst user interface. In accordance with a determination that the firstswipe gesture is in a first direction (e.g., rightward, as shown inFIGS. 5EK-5EL), the displayed first user interface is amini-application-object user interface 5140. The mini-application-objectuser interface 5140 includes one or more mini-application objects (e.g.,mini-application objects 583, 585, 587, and 589) that each provide asubset of functions of a corresponding application without launching thecorresponding application. In accordance with a determination that thefirst swipe gesture is in a second direction (e.g., leftward, as shownin FIGS. 5EQ-5ER), that is opposite the first direction, the displayedfirst user interface is a control panel user interface 5138. The controlpanel user interface 5138 includes one or more device controls (e.g.,flashlight control 5190 and camera control 5192) for controlling one ormore device functions of the device.

The wake screen user interface 504 has a fixed positional relationshiprelative to the mini-application-object screen 5140 and the controlpanel user interface 5138. Allowing the user to use directional gesturesto navigate to either the mini-application-object screen or the controlpanel user interface enhances the operability of the device (e.g., byreducing the number of controls displayed on a wake screen userinterface) and makes the user-device interface more efficient (e.g., byreducing visual clutter and reducing user mistakes due to the visualclutter), which, additionally, improves the battery life of the device.

In some embodiments, while the wake screen user interface 504 isdisplayed, the device displays (910) one or more notifications (e.g.,notification 5188, as shown in FIG. 5ED) on the wake screen userinterface. The device detects a second input for transitioning thedevice from an unauthenticated state to an authenticated state (e.g., asdescribed with regard to FIGS. 5FN-5FQ). In response to detecting thesecond input, the device displays, on the wake screen user interface504, restricted notification information corresponding to at least oneof the one or more notifications. For example, as shown in FIG. 5FT, anadditional notification 5234 is displayed and notification 5188 displaystext 5234 and image 5236 that were not displayed prior toauthentication. In some embodiments, restricted notification informationis, e.g., notification content and/or other notification informationthat is subject to restricted access by a setting, such as a privacyand/or security setting of the device. In some embodiments, therestricted notification information includes one or more notificationsthat are not displayed when the device is an unauthenticated state, suchas notifications from one or more applications with settings thatrestrict display of notifications when the device is in anunauthenticated state. In some embodiments, the restricted notificationinformation includes contextual information, such as earliercommunication content in a notification and/or calendar information fora range of time that corresponds to a time associated with a calendarappointment notification. In some embodiments, when the device is in theunlocked mode of the display-on state, the second user interfaceincludes longer versions of the notifications that are shown in thesecond user interface when the device is in the locked mode of thedisplay-on state. The longer version of a notification includes expandednotification content that, for example, includes all of the content inthe short version or standard version of the notification, and someadditional content that is not included in the short version or standardversion of the notification. In some embodiments, the expandednotification content includes more complete versions of the notificationcontent shown in the short version of the notification. In someembodiments, the expanded notification content includes images,interactive controls, and/or selectable options for performing actionswith respect to the notification, that are not included in the shortversions of the notification.

Displaying restricted notification information in response to detectinga second input for transitioning the device from an unauthenticatedstate to an authenticated state allows the device to provide a user withan indication that a notification was received without disclosing fullnotification information to unauthenticated individuals able to view thedevice display. This makes the user-device interface more efficient andenhances the operability of the device by allowing a user to viewinformation about incoming notifications without needing to wake thedevice (e.g., without jeopardizing the privacy of the notificationcontent).

In some embodiments, while displaying the first user interface inresponse to the first swipe gesture, the device detects (912) a secondswipe gesture (e.g., as shown in FIG. 5FN and or as shown in FIG. 5GC)in a third direction (e.g., upward, such as upward from a locationproximate to the lower edge of the display) that is perpendicular to thefirst direction and the second direction. In accordance with adetermination that the device is in an unauthenticated state, the devicedisplays an authentication user interface 518, as shown at FIG. 5FO. Inaccordance with a determination that the device is in an authenticatedstate, the device displays a second user interface. The second userinterface is a last displayed user interface that was displayed prior tothe display of the wake screen user interface (e.g., either a homescreen user interface or a user interface of an application). Forexample, FIG. 5GC is displayed when home screen user interface 522 wasthe last displayed user interface before wake screen user interface 504was displayed, so in response to the swipe input illustrated at FIG.5GC, home screen user interface 522 is redisplayed, as shown in FIG.5GD. In some embodiments if the home screen user interface 522 was thelast displayed user interface before the wake screen user interface 504was displayed, then a swipe up from the control center user interface5138 or mini application user interface 5140 reveals the home screenuser interface 522 and if an application user interface (e.g., mapapplication user interface 5154) was the last displayed user interfacebefore the wake screen user interface 504 was displayed, then the swipeup reveals the application user interface. In some embodiments, the wakescreen user interface 504 is displayed immediately upon waking thedevice, before authentication is made, and when authentication fails. Insome embodiments, an indicator (e.g., an open lock icon and/or textindicating an unlocked state) is displayed briefly on the wake screenupon authentication. In some embodiments, an indicator changes state(e.g., a lock icon changes state from a closed lock icon to an open lockicon) in accordance with a determination that authentication has beensuccessfully performed.

Redisplaying a last displayed user interface after dismissing the firstuser interface (e.g., the wake screen user interface/cover sheet userinterface) enhances the operability of the device by reducing the numberof steps needed to navigate back to the previous user interface, and theconsistent behavior also reduces user mistakes which makes theuser-device interface more efficient.

In some embodiments, in accordance with a determination that the seconduser interface is a home screen user interface 522, the device displays(914), in the home screen user interface, an object (e.g., navigationbanner 5160) that displays content from a first active application(e.g., an application that has updating content, such as an applicationthat last had focus and includes updating content, or an applicationthat has a highest priority among multiple applications that includesupdating content). In accordance with a determination that a state ofthe first active application has changed, the device updates the contentdisplayed in the object in accordance with the changed state of thefirst active application. For example, navigation content shown innavigation object 5160 (shown in pill form in FIGS. 5GM and 5GU) updates(e.g., in accordance with a determined change in location of thedevice). In some embodiments, navigation content shown in navigationobject 5160 (shown in banner form in FIGS. 5GP-5GQ) updates (e.g., inaccordance with a determined change in location of the device). In someembodiments, the object also includes a region 5182 that displays acurrent time. In some embodiments, the object on the home screen userinterface 522 is a “pill” (e.g., an object having a pill shape). In someembodiments, the object on the home screen user interface 522 isdisplayed in a region of the device display that is beyond a maindisplay area (e.g., a rectangular display area) of the display. In someembodiments, the object displays live directions from a maps applicationoperating in navigation mode. In some embodiments, the object displayslive playback information from a media player application operating inplayback mode. In some embodiments, the object displays live recordinginformation from a screen recording or video recording applicationoperating in recording mode. In some embodiments, the objectcorresponding to the first active application is also displayed when auser interface of a second active application distinct from the firstactive application is the currently displayed user interface.

Updating the content displayed in an object in the home screen userinterface in accordance with a changed state of an active applicationprovides information to a user from an active application withoutdisplaying the full application user interface. This makes theuser-device interface more efficient by allowing a user to determinethat an application is operating in an active mode without providinginput to navigate from the home screen to the application userinterface.

In some embodiments, while displaying the second user interface inresponse to the second swipe gesture, the device detects (916) a thirdswipe gesture (e.g., as shown at FIG. 5FR) in a fourth direction (e.g.,downward) that is opposite the third direction; and in response todetecting the third swipe gesture in the fourth direction, the deviceceases to display the second user interface (e.g., home screen userinterface 522) and redisplays the wake screen user interface 504 (e.g.,as shown in FIGS. 5FR-5FT).

In some embodiments, the control center user interface 5138 is displayedin response to a left swipe on the wake screen user interface 504 (e.g.,as shown at FIGS. 5EQ-5ES) both when the wake screen user interface 504is first displayed on waking the device, and when the wake screen userinterface 504 is subsequently redisplayed (e.g., as a cover sheet layerover an application user interface or over a home screen userinterface). In some embodiments, the mini-application-object userinterface 5140 is displayed in response to a right swipe on the wakescreen user interface 504 (e.g., as shown at FIGS. 5EK-5EM) both whenthe wake screen user interface 504 is first displayed, and when the wakescreen user interface 504 is subsequently redisplayed. In someembodiments, as the third swipe gesture in the fourth direction isreceived, the object on the home screen (the “pill”) morphs into asecond affordance (a floating banner) that is displayed on the wakescreen user interface 504 (e.g., as shown by navigation banner 5160 inFIGS. 5GM-5GP). The morphing includes, e.g., a change in the size of theobject, addition of content to the object (e.g., a direction icon 5180and/or text), and/or removal of content (e.g., a time 5182) from theobject.

Redisplaying the first user interface from any user interface (e.g., thehome screen user interface or an application user interface) using thesame gesture enhances the operability of the device (e.g., by reducingthe number of steps needed to navigate to the first user interface), andmakes the user-device interface more efficient (e.g., by providing aconsistent way to bring about the first user interface and therebyreducing user mistakes).

In some embodiments, the wake screen user interface is displayed (918)with an affordance (e.g., a navigation banner 5160) that displayscontent from a second active application (e.g., an application, that isthe same as the first active application or distinct from the firstactive application, that has updating content (such as an applicationthat last had focus and includes updating content, or an applicationthat has a highest priority among multiple applications that includesupdating content)). For example, navigation banner 5160 shown in FIG.5GP-5GQ includes updating content from maps application 5154. Whiledisplaying the wake screen user interface 504 with the affordance, inaccordance with a determination that a state of the second activeapplication has changed (e.g., a location of the device has changed,requiring an updated navigation instruction), the device updates thecontent displayed in the affordance in accordance with the changed stateof the second active application (as indicated by the changed contentfrom FIG. 5GP to FIG. 5GQ). For example, an affordance that correspondsto a maps application includes navigation information (such as next turninformation) that updates in real time, or an affordance thatcorresponds to a media player includes media playback information thatupdates in real time. In some embodiments, the wake screen userinterface 504 includes an intelligently selected app icon, e.g., ahand-off application. In some embodiments, the first affordance isdisplayed in addition to one or more additional objects on the wakescreen (e.g., in addition to time indicator, notification affordances,and/or device control affordances). In some embodiments, the contentfrom the active application displayed in the object (e.g., the pillobject) on the home screen user interface is a miniaturized version ofthe content displayed in the first affordance on the wake screen userinterface. For example, in comparison with content displayed in thefirst affordance on the wake screen, a miniaturized version of thecontent includes a reduced amount of text, text with reduced size, notext, a reduced number of icons, icons with reduced size, and/or noicons. In some embodiments, content displayed in the first affordance onthe wake screen includes navigation instruction text and a navigationinstruction icon having a first size, and the miniaturized version ofthe content includes no navigation instruction text and a navigationinstruction icon having a second size that is smaller than the firstsize.

Updating the content displayed in the affordance displayed in the wakescreen user interface in accordance with a changed state of an activeapplication provides information to a user from an active applicationwithout displaying the full application user interface. This makes theuser-device interface more efficient by allowing a user to receiveinformation from the application without providing input to navigatefrom the wake screen user interface to the application user interface.

In some embodiments, the wake screen user interface 504 includes (920) afirst control (e.g., flashlight control 5190 and/or camera control 5192)of the one or more device controls of the control panel user interface5138 (e.g., as shown in FIGS. 5ED and 5EW). In some embodiments, thefirst control is, e.g., a flashlight control 5190 that corresponds tothe flashlight control 5190 of the control panel user interface 5138.When operated, the flashlight control operates a device flashlight. Insome embodiments, the affordance is, a camera control 5192 or anotherpre-selected (e.g., user-selected) control. In some embodiments, thewake screen user interface 504 includes one or more regions (e.g., lowerleft and lower right corners) that display affordances for pre-selectedapps (e.g., a flashlight control icon 5190 and/or a camera applicationcontrol icon 5192). In some embodiments, the wake screen user interface504 includes at least one control affordance that does not correspond toa device control of the control panel user interface.

Providing controls from the control panel user interface on the wakescreen user interface allows the user to access the same controlfunctions from multiple locations, and thereby making the user-deviceinterface more efficient (e.g., by reducing the number of steps neededto navigate to the control).

In some embodiments, the first control requires (922) a first type ofinput to activate a first function while displayed on the wake screenuser interface and the first control requires a second type of input toactivate the first function while displayed on the control panel userinterface. In some embodiments, the first control requires differentinputs for activating the same function (e.g., a press input is requiredto toggle the flashlight control 5190 on the wake screen user interface504, as described with regard to FIGS. 5ED-5EJ, while a tap input isrequired to toggle the flashlight control 5190 in the control panel userinterface 5138, as described with regard to FIGS. 5ES-5EW. In someembodiments, a plurality of pre-selected affordances are displayed onthe wake screen. In some embodiments, the pre-selected affordances onthe wake screen are user-customizable.

Requiring a different input to activate a function from the wake screenthan the input that is required to activate the same function from thecontrol center prevents accidental operation of the function (e.g.,operation of the flashlight) when the phone wakes at a time that theuser does not intend to operate the phone. This saves battery life(e.g., by not using battery to operate the flashlight when theflashlight is not needed).

In some embodiments, the first control (e.g., camera control 5192) isalso displayed on the home screen user interface 522 (924), and a pressinput directed to the first control while displayed on the home screenuser interface causes display of a plurality of selectable options(e.g., as shown in menu 5220), and a press input directed to the firstcontrol while displayed on the wake screen user interface does not causedisplay of the plurality of selectable options.

Displaying a plurality of selectable options in response to press inputat control displayed on the home screen user interface and notdisplaying the plurality of selectable options when a press input isreceived at the same control displayed on the wake screen user interfaceprevents accidental access to functions among the plurality ofselectable options (e.g., taking a photo) when the phone wakes at a timethat the user does not intend to operate the phone. This saves batterylife (e.g., by not using battery to operate the camera when the camerais not needed).

In some embodiments, the wake screen has a plurality of luminositydisplay modes (e.g., bright mode, as shown in FIG. 5GV, and dark mode,as shown in FIG. 5GW) that are applied to one or more objects (e.g.,notifications 5160, 5188, 5234, and other platters and/or banners, suchas navigation banner 5160) displayed on the wake screen user interface504. In some embodiments, the device determines a luminosity of thebackground (e.g., by performing image analysis on a background image todetermine a luminosity value. The background image of the wake screenis, e.g., e a default background image or a user-selected backgroundimage). The luminosity display mode switches based on the luminosity ofthe background. For example, a color of at least a portion of an area ofone or more objects (e.g., a border around the object, a background ofthe object, text of the object, and/or an image displayed in the object)is changed when a luminosity mode changes (e.g., as described withregard to FIGS. 5GV-5GW). The change in color causes the object to havea greater degree of contrast with the background image to increase thevisibility of the object relative to the background image.

In some embodiments, while displaying the wake screen user interface,the device displays (926) a first object (e.g., a time-date indicator582) at a first position on the display 112 (e.g., the center of thefirst object is aligned with the horizontal symmetric center line of thedisplay 112). In accordance with the determination that the first swipegesture is in the first direction (e.g., as shown in FIGS. 5EK-5EL, thedevice displays the first object on the first user interface at a secondposition (e.g., as shown in FIG. 5EM) that is shifted in the firstdirection relative to the first position on the display). When the firstswipe is a right swipe, as shown in FIGS. 5EK-5EL, the time indicator582 is displayed on the right side of the mini-application-object userinterface 5140 (e.g., in FIG. 5EM) to provide a visual indication of theinput needed (a swipe to the left) to return to the wake screen. Inaccordance with the determination that the first swipe gesture is in thesecond direction (e.g., as shown at FIGS. 5EQ-5ER), the device displaysthe at least one object is at a third position (e.g., as shown in FIG.5ES) that is shifted in the second direction relative to the firstposition on the display (e.g., when the first swipe is a left swipe, thetime indicator 582 is displayed on the left side of the control paneluser interface 5138 to provide a visual indication of the input needed(a swipe to the right) to return to the wake screen).

Shifting a position of a first object (e.g., a time-date indicator) inresponse to swipe gesture input provides an indication of a location ofa current user interface relative to the wake screen user interface.Providing an indication of a location of a current user interfacerelative to the wake screen user interface reduces the number of inputsneeded to return to the wake screen user interface by reducing the needfor a user (e.g., a user that is new to the interface arrangement) toexperimentally swipe in order to recall the location of a desired userinterface relative to a current user interface.

It should be understood that the particular order in which theoperations in FIGS. 9A-9C have been described is merely an example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 600, 700, and 800) are also applicable in an analogous manner tomethod 900 described above with respect to FIGS. 9A-9C. For example, thecontacts, gestures, user interface objects, intensity thresholds, focusselectors, and animations described above with reference to method xxxoptionally have one or more of the characteristics of the contacts,gestures, user interface objects, intensity thresholds, focus selectors,and animations described herein with reference to other methodsdescribed herein (e.g., methods 600, 700, and 800). For brevity, thesedetails are not repeated here.

The operations described above with reference to FIGS. 9A-9C are,optionally, implemented by components depicted in FIGS. 1A-1B. Forexample, detection operation 902, transitioning operation 904, anddisplaying operation 908 are, optionally, implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive display 112, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A non-transitory computer readable storage mediumstoring one or more programs, the one or more programs comprisinginstructions which, when executed by an electronic device with a displayand a touch-sensitive surface, cause the electronic device to: while thedevice is in a screen-off state, receive one or more notifications;after receiving the one or more notifications, detect a first input froma user for waking the device from the screen-off state to a screen-onstate; in response to detecting the first input for waking the devicefrom the screen- off state to the screen-on state: transition the devicefrom the screen-off state to the screen-on state; display a wake screenuser interface on the display; and display the one or more notificationson the wake screen user interface; while displaying the wake screen userinterface and while at least one of the one or more notificationsremains displayed on the wake screen user interface, detect a secondinput for dismissing the wake screen user interface; in response todetecting the second input for dismissing the wake screen userinterface, cease to display the wake screen user interface and the atleast one of the one or more notifications; after ceasing to display thewake screen user interface and the at least one of the one or morenotifications in response to the second input, detect a third input forredisplaying the wake screen user interface; in response to detectingthe third input for redisplaying the wake screen user interface: inaccordance with a determination that the third input meetsnotification-clearance criteria, wherein the notification-clearancecriteria require that the third input is detected at a time that is (1)after a respective notification of the one or more notifications hasbeen cleared through direct user interaction with the respectivenotification or an application that corresponds to the respectivenotification and (2) after the device has transitioned from thescreen-on state to the screen-off state at least once since thedetection of the second input, redisplay the wake screen user interfacewithout displaying the at least one of the one or more notifications onthe redisplayed wake screen user interface; and in accordance with adetermination that the third input does not meet thenotification-clearance criteria: redisplay the wake screen userinterface, and redisplay the at least one of the one or morenotifications on the redisplayed wake screen user interface.
 2. Thestorage medium of claim 1, including instructions which, when executedby the electronic device, cause the electronic device to: in response todetecting the third input for redisplaying the wake screen userinterface, and in accordance with the determination that the third inputdoes not meet the notification-clearance criteria: in accordance with adetermination that one or more notification-clearance interactions haveoccurred, forgo display of one or more notifications that are cleared bythe one or more notification-clearance interactions on the redisplayedwake screen user interface.
 3. The storage medium of claim 1, includinginstructions which, when executed by the electronic device, cause theelectronic device to: after detecting the first input for waking thedevice from the screen-off state to the screen-on state and prior todetecting the second input for dismissing the wake screen userinterface: detect a plurality of intermediate inputs, the plurality ofintermediate inputs including: a first intermediate input for dismissingthe wake screen user interface, and a second intermediate input forredisplaying the wake screen user interface.
 4. The storage medium ofclaim 1, wherein: the second input for dismissing the wake screen userinterface is an input for displaying a first user interface that isdistinct from the wake screen user interface, the first user interfaceis displayed in response to the second input, and the third input forredisplaying the wake screen user interface is received while the firstuser interface is displayed.
 5. The storage medium of claim 1, wherein:the third input for redisplaying the wake screen user interface isreceived while a content playback application is active, andredisplaying the wake screen user interface includes displaying at leastone media playback control in the wake screen user interface.
 6. Thestorage medium of claim 1, including instructions which, when executedby the electronic device, cause the electronic device to: while the wakescreen user interface is displayed, detect a fourth input by a contacton the touch-sensitive surface, including detecting movement of thecontact along the touch-sensitive surface in a first direction anddetecting lift-off of the contact after the movement; and in response todetecting the fourth input: move at least one object displayed on thewake screen user interface in accordance with the movement of thecontact; and, reverse the movement of the at least one object uponlift-off of the contact.
 7. The storage medium of claim 1, includinginstructions which, when executed by the electronic device, cause theelectronic device to: while displaying the one or more notifications onthe wake screen user interface, detect a fifth input by a contact on thetouch-sensitive surface at a location that corresponds to a firstnotification of the one or more notifications; and, in response todetecting the fifth input: cease to display the wake screen userinterface; and display a first application user interface for a firstapplication that corresponds to the first notification.
 8. The storagemedium of claim 7, including instructions which, when executed by theelectronic device, cause the electronic device to: while displaying thefirst application user interface for the first application thatcorresponds to the first notification, detect a sixth input forredisplaying the wake screen user interface; in response to detectingthe sixth input for redisplaying the wake screen user interface: ceaseto display the first application user interface, display the wake screenuser interface, display at least one second notification of the one ormore notifications on the wake screen user interface, wherein the atleast one second notification corresponds to a second application thatis distinct from the first application, and forgo display of the firstnotification on the wake screen user interface with the at least onesecond notification.
 9. The storage medium of claim 8, includinginstructions which, when executed by the electronic device, cause theelectronic device to: after detecting the sixth input, while displayingthe wake screen user interface, detect a seventh input for dismissingthe wake screen user interface; and in response to detecting the seventhinput for dismissing the wake screen user interface: cease to displaythe wake screen user interface, and redisplay the first application userinterface for the first application.
 10. The storage medium of claim 9,including instructions which, when executed by the electronic device,cause the electronic device to: while the first application userinterface for the first application is redisplayed, detect an eighthinput for invoking a third application that is distinct from the firstapplication and the second application; and in response to detecting theeighth input for invoking the third application: display a thirdapplication user interface of the third application; after detecting theeighth input, while displaying the third application user interface,detect a ninth input for redisplaying the wake screen user interface; inresponse to detecting the ninth input for redisplaying the wake screenuser interface: cease to display the third application user interface;display the wake screen user interface; and redisplay the at least onesecond notification of the one or more notifications on the wake screenuser interface without redisplaying the first notification.
 11. Thestorage medium of claim 8, including instructions which, when executedby the electronic device, cause the electronic device to: afterdisplaying the at least one second notification without displaying thefirst notification on the wake screen user interface, detect a firsttransition from the screen-on state to the screen-off state followed bya second transition from the screen-off state to the screen-on state;and, in response to detecting the first transition followed by thesecond transition: redisplay the wake screen user interface withoutdisplaying any of the one or more notifications on the wake screen userinterface.
 12. The storage medium of claim 1, including instructionswhich, when executed by the electronic device, cause the electronicdevice to: while displaying the wake screen user interface with all ofthe one or more notifications, detect a third transitioning from thescreen-on state to the screen-off state followed by a fourth transitionfrom the screen-off state to the screen-on state; and, in response todetecting the third transition followed by the fourth transition:redisplay the wake screen user interface with the one or morenotifications on the wake screen user interface.
 13. The storage mediumof claim 1, including instructions which, when executed by theelectronic device, cause the electronic device to: while displaying thewake screen user interface with the one or more notifications, detect atenth input for displaying an authentication user interface; in responseto detecting the tenth input for displaying the authentication userinterface: cease to display the wake screen user interface; and displaythe authentication user interface; while the authentication userinterface is displayed, detect an authorization input; in accordancewith a determination that the authorization input is valid, display asecond user interface; while displaying the second user interface,detect an eleventh input for redisplaying the wake screen userinterface; and, in response to detecting the eleventh input: cease todisplay the second application user interface; and redisplay the wakescreen user interface with the one or more notifications.
 14. Thestorage medium of claim 1, including instructions which, when executedby the electronic device, cause the electronic device to: in accordancewith the determination that the third input meets thenotification-clearance criteria, add, to a set of recent notifications,one or more cleared notifications that correspond to the at least one ofthe one or more notifications not displayed on the wake screen userinterface.
 15. The storage medium of claim 14, including instructionswhich, when executed by the electronic device, cause the electronicdevice to: after adding the one or more cleared notifications to the setof recent notifications, while the wake screen user interface isdisplayed, detect a twelfth input; and in response to detecting thetwelfth input, in accordance with a determination that the twelfth inputmeets recent-notification-display criteria, display at least a portionof the set of recent notifications.
 16. An electronic device,comprising: a display; a touch-sensitive surface; one or moreprocessors; memory; and one or more programs, wherein the one or moreprograms are stored in the memory and configured to be executed by theone or more processors, the one or more programs including instructionsfor: while the device is in a screen-off state, receiving one or morenotifications; after receiving the one or more notifications, detectinga first input from a user for waking the device from the screen-offstate to a screen-on state; in response to detecting the first input forwaking the device from the screen- off state to the screen-on state:transitioning the device from the screen-off state to the screen-onstate; displaying a wake screen user interface on the display; anddisplaying the one or more notifications on the wake screen userinterface; while displaying the wake screen user interface and while atleast one of the one or more notifications remains displayed on the wakescreen user interface, detecting a second input for dismissing the wakescreen user interface; in response to detecting the second input fordismissing the wake screen user interface, ceasing to display the wakescreen user interface and the at least one of the one or morenotifications; after ceasing to display the wake screen user interfaceand the at least one of the one or more notifications in response to thesecond input, detecting a third input for redisplaying the wake screenuser interface; in response to detecting the third input forredisplaying the wake screen user interface: in accordance with adetermination that the third input meets notification-clearancecriteria, wherein the notification-clearance criteria require that thethird input is detected at a time that is (1) after a respectivenotification of the one or more notifications has been cleared throughdirect user interaction with the respective notification or anapplication that corresponds to the respective notification and (2)after the device has transitioned from the screen-on state to thescreen-off state at least once since the detection of the second input,redisplaying the wake screen user interface without displaying the atleast one of the one or more notifications on the redisplayed wakescreen user interface; and in accordance with a determination that thethird input does not meet the notification-clearance criteria:redisplaying the wake screen user interface, and redisplaying the atleast one of the one or more notifications on the redisplayed wakescreen user interface.
 17. A method, comprising: at a device having adisplay and a touch-sensitive surface: while the device is in ascreen-off state, receiving one or more notifications; after receivingthe one or more notifications, detecting a first input from a user forwaking the device from the screen-off state to a screen-on state; inresponse to detecting the first input for waking the device from thescreen-off state to the screen-on state: transitioning the device fromthe screen-off state to the screen-on state; displaying a wake screenuser interface on the display; and displaying the one or morenotifications on the wake screen user interface; while displaying thewake screen user interface and while at least one of the one or morenotifications remains displayed on the wake screen user interface,detecting a second input for dismissing the wake screen user interface;in response to detecting the second input for dismissing the wake screenuser interface, ceasing to display the wake screen user interface andthe at least one of the one or more notifications; after ceasing todisplay the wake screen user interface and the at least one of the oneor more notifications in response to the second input, detecting a thirdinput for redisplaying the wake screen user interface; in response todetecting the third input for redisplaying the wake screen userinterface: in accordance with a determination that the third input meetsnotification-clearance criteria, wherein the notification-clearancecriteria require that the third input is detected at a time that is (1)after a respective notification of the one or more notifications hasbeen cleared through direct user interaction with the respectivenotification or an application that corresponds to the respectivenotification and (2) after the device has transitioned from thescreen-on state to the screen-off state at least once since thedetection of the second input, redisplaying the wake screen userinterface without displaying the at least one of the one or morenotifications on the redisplayed wake screen user interface; and inaccordance with a determination that the third input does not meet thenotification-clearance criteria: redisplaying the wake screen userinterface, and redisplaying the at least one of the one or morenotifications on the redisplayed wake screen user interface.
 18. Theelectronic device of claim 16, wherein the one or more programs includeinstructions for: in response to detecting the third input forredisplaying the wake screen user interface, and in accordance with thedetermination that the third input does not meet thenotification-clearance criteria: in accordance with a determination thatone or more notification-clearance interactions have occurred, forgoingdisplay of one or more notifications that are cleared by the one or morenotification-clearance interactions on the redisplayed wake screen userinterface.
 19. The electronic device of claim 16, wherein the one ormore programs include instructions for: after detecting the first inputfor waking the device from the screen-off state to the screen-on stateand prior to detecting the second input for dismissing the wake screenuser interface: detecting a plurality of intermedia inputs, theplurality of intermedia inputs including: a first intermedia input fordismissing the wake screen user interface, and a second intermedia inputfor redisplaying the wake screen user interface.
 20. The electronicdevice of claim 16, wherein: the second input for dismissing the wakescreen user interface is an input for displaying a first user interfacethat is distinct from the wake screen user interface, the first userinterface is displayed in response to the second input, and the thirdinput for redisplaying the wake screen user interface is received whilethe first user interface is displayed.
 21. The electronic device ofclaim 16, wherein: the third input for redisplaying the wake screen userinterface is received while a content playback application is active;and redisplaying the wake screen user interface includes displaying atleast one media playback control in the wake screen user interface. 22.The electronic device of claim 16, wherein the one or more programsinclude instructions for: while the wake screen user interface isdisplayed, detecting a fourth input by a contact on the touch-sensitivesurface, including detecting movement of the contact along thetouch-sensitive surface in a first direction and detecting lift-off ofthe contact after the movement; and in response to detecting the fourthinput: moving at least one object displayed on the wake screen userinterface in accordance with the movement of the contact; and, reversingthe movement of the at least one object upon lift-off of the contact.23. The electronic device of claim 16, wherein the one or more programsinclude instructions for: while displaying the one or more notificationson the wake screen user interface, detecting a fifth input by a contacton the touch-sensitive surface at a location that corresponds to a firstnotification of the one or more notifications; and, in response todetecting the fifth input: ceasing to display the wake screen userinterface; and displaying a first application user interface for a firstapplication that corresponds to the first notification.
 24. Theelectronic device of claim 23, wherein the one or more programs includeinstructions for: while displaying the first application user interfacefor the first application that corresponds to the first notification,detecting a sixth input for redisplaying the wake screen user interface;in response to detecting the sixth input for redisplaying the wakescreen user interface: ceasing to display the first application userinterface, displaying the wake screen user interface, displaying atleast one second notification of the one or more notification on thewake screen user interface, wherein the at least one second notificationcorresponds to a second application that is distinct from the firstapplication, and forgoing display of the first notification on the wakescreen user interface with the at least one second notification.
 25. Theelectronic device of claim 24, wherein the one or more programs includeinstructions for: after detecting the sixth input, while displaying thewake screen user interface, detecting a seventh input for dismissing thewake screen user interface; and in response to detecting the seventhinput for dismissing the wake screen user interface: ceasing to displaythe wake screen user interface, and redisplaying the first applicationuser interface for the first application.
 26. The electronic device ofclaim 25, wherein the one or more programs include instructions for:while the first application user interface for the first application isredisplayed, detecting an eighth input for invoking a third applicationthat is distinct from the first application and the second application;and in response to detecting the eighth input for invoking the thirdapplication: displaying a third application user interface of the thirdapplication; after detecting the eighth input, while displaying thethird application user interface, detecting a ninth input forredisplaying the wake screen user interface; in response to detectingthe ninth input for redisplaying the wake screen user interface: ceasingto display the third application user interface; displaying the wakescreen user interface; and redisplaying the at least one secondnotification of the one or more notifications on the wake screen userinterface without redisplaying the first notification.
 27. Theelectronic device of claim 24, wherein the one or more programs includeinstructions for: after displaying the at least one second notificationwithout displaying the first notification on the wake screen userinterface, detecting a first transition from the screen-on state to thescreen-off state followed by a second transition from the screen-offstate to the screen-on state; and, in response to detecting the firsttransition followed by the second transition: redisplaying the wakescreen user interface without displaying any of the one or morenotifications on the wake screen user interface.
 28. The electronicdevice of claim 16, wherein the one or more programs includeinstructions for: while displaying the wake screen user interface withall of the one or more notifications, detecting a third transitioningfrom the screen-on state to the screen-off state followed by a fourthtransition from the screen-off state to the screen-on state; and, inresponse to detecting the third transition followed by the fourthtransition: redisplaying the wake screen user interface with the one ormore notifications on the wake screen user interface.
 29. The electronicdevice of claim 16, wherein the one or more programs includeinstructions for: while displaying the wake screen user interface withthe one or more notifications, detecting a tenth input for displaying anauthentication user interface; in response to detecting the tenth inputfor displaying the authentication user interface: ceasing to display thewake screen user interface; and displaying the authentication userinterface; while the authentication user interface is displayed,detecting an authorization input; in accordance with a determinationthat the authorization input is valid, displaying a second userinterface; while displaying the second user interface, detecting aneleventh input for redisplaying the wake screen user interface; and, inresponse to detecting the eleventh input: ceasing to display the secondapplication user interface; and redisplaying the wake screen userinterface with the one or more notifications.
 30. The electronic deviceof claim 16, wherein the one or more programs include instructions for:in accordance with the determination that the third input meets thenotification-clearance criteria, adding, to a set of recentnotifications, one or more cleared notifications that correspond to theat least one of the one or more notifications not displayed on the wakescreen user interface.
 31. The electronic device of claim 30, whereinthe one or more programs include instructions for: after adding the oneor more cleared notifications to the set of recent notifications, whilethe wake screen user interface is displayed, detecting a twelfth input;and in response to detecting the twelfth input, in accordance with adetermination that the twelfth input meets recent-notification-displaycriteria, displaying at least a portion of the set of recentnotifications.
 32. The method of claim 17, including: in response todetecting the third input for redisplaying the wake screen userinterface, and in accordance with the determination that the third inputdoes not meet the notification-clearance criteria: in accordance with adetermination that one or more notification-clearance interactions haveoccurred, forgoing display of one or more notifications that are clearedby the one or more notification-clearance interactions on theredisplayed wake screen user interface.
 33. The method of claim 17,including: after detecting the first input for waking the device fromthe screen-off state to the screen-on state and prior to detecting thesecond input for dismissing the wake screen user interface: detecting aplurality of intermedia inputs, the plurality of intermedia inputsincluding: a first intermedia input for dismissing the wake screen userinterface, and a second intermedia input for redisplaying the wakescreen user interface.
 34. The method of claim 17, wherein: the secondinput for dismissing the wake screen user interface is an input fordisplaying a first user interface that is distinct from the wake screenuser interface, the first user interface is displayed in response to thesecond input, and the third input for redisplaying the wake screen userinterface is received while the first user interface is displayed. 35.The method of claim 17, wherein: the third input for redisplaying thewake screen user interface is received while a content playbackapplication is active, and redisplaying the wake screen user interfaceincludes displaying at least one media playback control in the wakescreen user interface.
 36. The method of claim 17, including: while thewake screen user interface is displayed, detecting a fourth input by acontact on the touch-sensitive surface, including detecting movement ofthe contact along the touch-sensitive surface in a first direction anddetecting lift-off of the contact after the movement; and in response todetecting the fourth input: moving at least one object displayed on thewake screen user interface in accordance with the movement of thecontact; and, reversing the movement of the at least one object uponlift-off of the contact.
 37. The method of claim 17, including: whiledisplaying the one or more notifications on the wake screen userinterface, detecting a fifth input by a contact on the touch-sensitivesurface at a location that corresponds to a first notification of theone or more notifications; and, in response to detecting the fifthinput: ceasing to display the wake screen user interface; and displayinga first application user interface for a first application thatcorresponds to the first notification.
 38. The method of claim 37,including: while displaying the first application user interface for thefirst application that corresponds to the first notification, detectinga sixth input for redisplaying the wake screen user interface; inresponse to detecting the sixth input for redisplaying the wake screenuser interface: ceasing to display the first application user interface,displaying the wake screen user interface, displaying at least onesecond notification of the one or more notification on the wake screenuser interface, wherein the at least one second notification correspondsto a second application that is distinct from the first application, andforgoing display of the first notification on the wake screen userinterface with the at least one second notification.
 39. The method ofclaim 38, including: after detecting the sixth input, while displayingthe wake screen user interface, detecting a seventh input for dismissingthe wake screen user interface; and in response to detecting the seventhinput for dismissing the wake screen user interface: ceasing to displaythe wake screen interface, and redisplaying the first application userinterface for the first application.
 40. The method of claim 39,including: while the first application user interface for the firstapplication is redisplayed, detecting an eighth input for invoking athird application that is distinct from the first application and thesecond application; and in response to detecting the eighth input forinvoking the third application: displaying a third application userinterface of the third application; after detecting the eighth input,while displaying the third application user interface, detecting a ninthinput for redisplaying the wake screen user interface; in response todetecting the ninth input for redisplaying the wake screen userinterface: ceasing to display the third application user interface;displaying the wake screen user interface; and redisplaying the at leastone second notification of the one or more modifications on the wakescreen user interface without redisplaying the first notification. 41.The method of claim 38, including: after displaying the at least onesecond notification without displaying the first notification on thewake screen user interface, detecting a first transition from thescreen-on state to the screen-off state followed by a second transitionfrom the screen-off state to the screen-on state; and, in response todetecting the first transition followed by the second transition:redisplaying the wake screen user interface without displaying any ofthe one or more notifications on the wake screen user interface.
 42. Themethod of claim 17, including: while displaying the wake screen userinterface with all of the one or more notifications, detecting a thirdtransitioning from the screen-on state to the screen-off state followedby a fourth transition from the screen-off state to the screen-on state;and, in response to detecting the third transition followed by thefourth transition: redisplaying the wake screen user interface with theone or more notifications on the wake screen user interface.
 43. Themethod of claim 17, including: while displaying the wake screen userinterface with the one or more notifications, detecting a tenth inputfor displaying an authentication user interface; in response todetecting the tenth input for displaying the authentication userinterface: ceasing to display the wake screen user interface; anddisplaying the authentication user interface; while the authenticationuser interface is displayed, detecting an authorization input; inaccordance with a determination that the authorization input is valid,displaying a second user interface; while displaying the second userinterface, detecting an eleventh input for redisplaying the wake screenuser interface; and in response to detecting the eleventh input: ceasingto display the second application user interface; and redisplaying thewake screen user interface with the one or more notifications.
 44. Themethod of claim 17, including: in accordance with the determination thatthe third input meets the notification-clearance criteria, adding, to aset of recent notifications, one or more cleared notifications thatcorrespond to the at least one of the one or more notifications notdisplayed on the wake screen user interface.
 45. The method of claim 44,including: after adding the one or more cleared notifications to the setof recent notifications, while the wake screen user interface isdisplayed, detecting a twelfth input; and in response to detecting thetwelfth input, in accordance with a determination that the twelfth inputmeets recent-notification-display criteria, displaying at least aportion of the set of recent notifications.